- 04 7月, 2000 3 次提交
-
-
由 Tom Lane 提交于
Don't go through pg_exec_query_dest(), but directly to the execution routines. Also, extend parameter lists so that there's no need to change the global setting of allowSystemTableMods, a hack that was certain to cause trouble in the event of any error.
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
parsing to not clobber the optarg string -- so that we can bring SetOptsFile() up to speed.
-
- 29 6月, 2000 1 次提交
-
-
由 Tom Lane 提交于
in copyfuncs and equalfuncs exposed by regression tests. We still have some work to do: these modules really ought to handle most or all of the utility statement node types. But it's better than it was.
-
- 28 6月, 2000 1 次提交
-
-
由 Tom Lane 提交于
for details). It doesn't really do that much yet, since there are no short-term memory contexts in the executor, but the infrastructure is in place and long-term contexts are handled reasonably. A few long- standing bugs have been fixed, such as 'VACUUM; anything' in a single query string crashing. Also, out-of-memory is now considered a recoverable ERROR, not FATAL. Eliminate a large amount of crufty, now-dead code in and around memory management. Fix problem with holding off SIGTRAP, SIGSEGV, etc in postmaster and backend startup.
-
- 23 6月, 2000 1 次提交
-
-
由 Peter Eisentraut 提交于
option settings. Sort out SIGHUP vs BACKEND -- there is no total ordering here, so make explicit checks. Add comments explaining all of this. Removed permissions check on SHOW command. Add examine_subclass to the game, rename to SQL_inheritance to fit the official data model better. Adjust documentation. Standalone backend needs to reset all options before it starts. To facilitate that, have IsUnderPostmaster be set by the postmaster itself, don't wait for the magic -p switch. Also make sure that all environment variables and argv's survive init_ps_display(). Use strdup where necessary. Have initdb make configuration files (postgresql.conf, pg_hba.conf) mode 0600 -- having configuration files is no fun if you can't edit them.
-
- 15 6月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 09 6月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 04 6月, 2000 1 次提交
-
-
由 Peter Eisentraut 提交于
Install a default configuration file. Clean up some funny business in the config file code.
-
- 31 5月, 2000 1 次提交
-
-
由 Peter Eisentraut 提交于
That means you can now set your options in either or all of $PGDATA/configuration, some postmaster option (--enable-fsync=off), or set a SET command. The list of options is in backend/utils/misc/guc.c, documentation will be written post haste. pg_options is gone, so is that pq_geqo config file. Also removed were backend -K, -Q, and -T options (no longer applicable, although -d0 does the same as -Q). Added to configure an --enable-syslog option. changed all callers from TPRINTF to elog(DEBUG)
-
- 29 5月, 2000 1 次提交
-
-
由 Tom Lane 提交于
the src/include tree, so that -I backend is no longer necessary anywhere. Also, clean up some bit rot in contrib tree.
-
- 21 5月, 2000 1 次提交
-
-
由 Tom Lane 提交于
defined then statistics about memory usage of all the global memory contexts are printed after each commit.
-
- 01 5月, 2000 1 次提交
-
-
由 Tom Lane 提交于
cleanup, ie, as soon as we have caught the longjmp. This ensures that current context will be a valid context throughout error cleanup. Before it was possible that current context was pointing at a context that would get deleted during cleanup, leaving any subsequent pallocs in deep trouble. I was able to provoke an Assert failure when compiled with asserts + -DCLOBBER_FREED_MEMORY, if I did something that would cause an error to be reported by the backend large-object code, because indeed that code operates in a context that gets deleted partway through xact abort --- and CurrentMemoryContext was still pointing at it! Boo hiss.
-
- 28 4月, 2000 1 次提交
-
-
由 Tom Lane 提交于
because StatFp never got set in that case. Set it immediately before use to eliminate such problems.
-
- 23 4月, 2000 1 次提交
-
-
由 Tom Lane 提交于
fsync settings, so the -F option no longer needs to be treated as secure.
-
- 13 4月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 05 4月, 2000 2 次提交
-
-
由 Tom Lane 提交于
xact abort state in pg_exec_query_dest, we should continue scanning the querytree list, on the off chance that one of the later queries in the string is COMMIT or ROLLBACK.
-
由 Tom Lane 提交于
would crash, due to premature invocation of SetQuerySnapshot(). Clean up problems with handling of multiple queries by splitting pg_parse_and_plan into two routines. The old code would not, for example, do the right thing with END; SELECT... submitted in one query string when it had been in transaction abort state, because it'd decide to skip planning the SELECT before it had executed the END. New arrangement is simpler and doesn't force caller to plan if only parse+rewrite is needed.
-
- 24 3月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
easy (maybe dumb) fix for 5 in attachment define.patch greetings, Andreas
-
- 01 3月, 2000 1 次提交
-
-
由 Tatsuo Ishii 提交于
-
- 22 2月, 2000 1 次提交
-
-
由 Hiroshi Inoue 提交于
-
- 21 2月, 2000 1 次提交
-
-
由 Hiroshi Inoue 提交于
* Allow PQrequestCancel() to terminate when in waiting-for-lock state Changes are limited to BACKEND,however.
-
- 20 2月, 2000 2 次提交
-
-
由 Tom Lane 提交于
command line processing. As it stood, a bogus PGOPTIONS value from a client would force a database system restart. Not bad as a denial- of-service attack...
-
由 Tom Lane 提交于
variable, instead calling same code in variable.c that is used to parse SET DATESTYLE. Fix bug: although backend's startup datestyle had been changed to ISO, 'RESET DATESTYLE' and 'SET DATESTYLE TO DEFAULT' didn't know about it. For consistency I have made the latter two reset to the PGDATESTYLE-defined initial value, which may not be the same as the compiled-in default of ISO.
-
- 18 2月, 2000 1 次提交
-
-
由 Hiroshi Inoue 提交于
-
- 26 1月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
* Portions Copyright (c) 1996-2000, PostgreSQL, Inc to all files copyright Regents of Berkeley. Man, that's a lot of files.
-
- 23 1月, 2000 1 次提交
-
-
由 Tom Lane 提交于
pghackers discussion of 5-Jan-2000. The amopselect and amopnpages estimators are gone, and in their place is a per-AM amcostestimate procedure (linked to from pg_am, not pg_amop).
-
- 09 1月, 2000 1 次提交
-
-
由 Tatsuo Ishii 提交于
-
- 22 12月, 1999 1 次提交
-
-
由 Hiroshi Inoue 提交于
to live in a transaction before access to db during backend startup.
-
- 16 11月, 1999 1 次提交
-
-
由 Tom Lane 提交于
Warn_restart has been set by the backend main loop. This means that elog(ERROR) or elog(FATAL) in the postmaster or during backend startup now have well-defined behavior: proc_exit() rather than coredump. In the case of elog() inside the postmaster, I think that proc_exit() is probably not enough --- don't we want our child backends to be forced to quit too? But I don't understand Vadim's recent changes in this area, so I'll leave it to him to look over and tweak if needed.
-
- 25 10月, 1999 1 次提交
-
-
由 Tom Lane 提交于
eliminating some wildly inconsistent coding in various parts of the system. I set MAXPGPATH = 1024 in config.h.in. If anyone is really convinced that there ought to be a configure-time test to set the value, go right ahead ... but I think it's a waste of time.
-
- 23 10月, 1999 1 次提交
-
-
由 Tom Lane 提交于
pg_dump and interfaces/odbc still need some work.)
-
- 08 10月, 1999 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
up debugging options for postmaster and postgres programs. postmaster -d is no longer optional. Documentation updates.
-
- 07 10月, 1999 1 次提交
-
-
由 Vadim B. Mikheev 提交于
First step in cleaning up backend initialization code. Fix for FATAL: now FATAL is ERROR + exit.
-
- 30 9月, 1999 1 次提交
-
-
由 Jan Wieck 提交于
Implements the CREATE CONSTRAINT TRIGGER and SET CONSTRAINTS commands. TODO: Generic builtin trigger procedures Automatic execution of appropriate CREATE CONSTRAINT... at CREATE TABLE Support of new trigger type in pg_dump Swapping of huge # of events to disk Jan
-
- 24 9月, 1999 1 次提交
-
-
由 Tom Lane 提交于
* Buffer refcount cleanup (per my "progress report" to pghackers, 9/22). * Add links to backend PROC structs to sinval's array of per-backend info, and use these links for routines that need to check the state of all backends (rather than the slow, complicated search of the ShmemIndex hashtable that was used before). Add databaseOID to PROC structs. * Use this to implement an interlock that prevents DESTROY DATABASE of a database containing running backends. (It's a little tricky to prevent a concurrently-starting backend from getting in there, since the new backend is not able to lock anything at the time it tries to look up its database in pg_database. My solution is to recheck that the DB is OK at the end of InitPostgres. It may not be a 100% solution, but it's a lot better than no interlock at all...) * In ALTER TABLE RENAME, flush buffers for the relation before doing the rename of the physical files, to ensure we don't get failures later from mdblindwrt(). * Update TRUNCATE patch so that it actually compiles against current sources :-(. You should do "make clean all" after pulling these changes.
-
- 31 8月, 1999 1 次提交
-
-
由 Tom Lane 提交于
backend. Still much left to do.
-
- 22 7月, 1999 1 次提交
-
-
由 Tom Lane 提交于
unexpected loss of connection to frontend.
-