- 13 Jul, 2002 1 commit
-
-
Bruce Momjian authored
zero turns off the timer.
-
- 16 Jun, 2002 1 commit
-
-
Bruce Momjian authored
-
- 15 Jun, 2002 1 commit
-
-
Bruce Momjian authored
-
- 08 Jun, 2002 1 commit
-
-
Bruce Momjian authored
-
- 17 May, 2002 1 commit
-
-
Tom Lane authored
GUC support. It's now possible to set datestyle, timezone, and client_encoding from postgresql.conf and per-database or per-user settings. Also, implement rollback of SET commands that occur in a transaction that later fails. Create a SET LOCAL var = value syntax that sets the variable only for the duration of the current transaction. All per previous discussions in pghackers.
-
- 04 Apr, 2002 1 commit
-
-
Bruce Momjian authored
-
- 01 Apr, 2002 1 commit
-
-
Tom Lane authored
path. The default behavior if no per-user schemas are created is that all users share a 'public' namespace, thus providing behavior backwards compatible with 7.2 and earlier releases. Probably the semantics and default setting will need to be fine-tuned, but this is a start.
-
- 24 Mar, 2002 1 commit
-
-
Tom Lane authored
Also, fix debug logging of parse/plan trees so that the messages actually go through elog(), not directly to stdout.
-
- 09 Mar, 2002 1 commit
-
-
Bruce Momjian authored
file that SIGHUP or "pg_ctl reload" are required for changes to take affect on a running server.
-
- 06 Mar, 2002 1 commit
-
-
Bruce Momjian authored
o Change all current CVS messages of NOTICE to WARNING. We were going to do this just before 7.3 beta but it has to be done now, as you will see below. o Change current INFO messages that should be controlled by client_min_messages to NOTICE. o Force remaining INFO messages, like from EXPLAIN, VACUUM VERBOSE, etc. to always go to the client. o Remove INFO from the client_min_messages options and add NOTICE. Seems we do need three non-ERROR elog levels to handle the various behaviors we need for these messages. Regression passed.
-
- 03 Mar, 2002 1 commit
-
-
Bruce Momjian authored
-
- 02 Mar, 2002 1 commit
-
-
Bruce Momjian authored
now just below FATAL in server_min_messages. Added more text to highlight ordering difference between it and client_min_messages. --------------------------------------------------------------------------- REALLYFATAL => PANIC STOP => PANIC New INFO level the prints to client by default New LOG level the prints to server log by default Cause VACUUM information to print only to the client NOTICE => INFO where purely information messages are sent DEBUG => LOG for purely server status messages DEBUG removed, kept as backward compatible DEBUG5, DEBUG4, DEBUG3, DEBUG2, DEBUG1 added DebugLvl removed in favor of new DEBUG[1-5] symbols New server_min_messages GUC parameter with values: DEBUG[5-1], INFO, NOTICE, ERROR, LOG, FATAL, PANIC New client_min_messages GUC parameter with values: DEBUG[5-1], LOG, INFO, NOTICE, ERROR, FATAL, PANIC Server startup now logged with LOG instead of DEBUG Remove debug_level GUC parameter elog() numbers now start at 10 Add test to print error message if older elog() values are passed to elog() Bootstrap mode now has a -d that requires an argument, like postmaster
-
- 18 Feb, 2002 1 commit
-
-
Bruce Momjian authored
-
- 04 Jan, 2002 1 commit
-
-
Bruce Momjian authored
-
- 17 Dec, 2001 1 commit
-
-
Bruce Momjian authored
-
- 30 Sep, 2001 1 commit
-
-
Tom Lane authored
upper limit on what we will believe from sysconf(_SC_OPEN_MAX). The default value is 1000, so that under ordinary conditions it won't affect the behavior. But on platforms where the kernel promises far more than it can deliver, this can be used to prevent running out of file descriptors. See numerous past discussions, eg, pgsql-hackers around 23-Dec-2000.
-
- 29 Sep, 2001 1 commit
-
-
Tom Lane authored
existing lock manager and spinlocks: it understands exclusive vs shared lock but has few other fancy features. Replace most uses of spinlocks with lightweight locks. All remaining uses of spinlocks have very short lock hold times (a few dozen instructions), so tweak spinlock backoff code to work efficiently given this assumption. All per my proposal on pghackers 26-Sep-01.
-
- 27 Sep, 2001 1 commit
-
-
Bruce Momjian authored
-
- 23 Sep, 2001 1 commit
-
-
Peter Eisentraut authored
-
- 21 Sep, 2001 2 commits
-
-
Tom Lane authored
a hung client or lost connection can't indefinitely block a postmaster child (not to mention the possibility of deliberate DoS attacks). Timeout is controlled by new authentication_timeout GUC variable, which I set to 60 seconds by default ... does that seem reasonable?
-
Tom Lane authored
piggybacking on SortMem. Add documentation for some recently-added GUC parameters that had so far escaped it.
-
- 12 Sep, 2001 1 commit
-
-
Peter Eisentraut authored
max_locks_per_xact.
-
- 07 Sep, 2001 1 commit
-
-
Tom Lane authored
max_connections.
-
- 21 Aug, 2001 2 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
-
- 15 Aug, 2001 1 commit
-
-
Bruce Momjian authored
Allow pg_shadow to be MD5 encrypted. Add ENCRYPTED/UNENCRYPTED option to CREATE/ALTER user. Add password_encryption postgresql.conf option. Update wire protocol version to 2.1.
-
- 05 Jul, 2001 1 commit
-
-
Jan Wieck authored
Jan
-
- 30 Jun, 2001 1 commit
-
-
Peter Eisentraut authored
characteristics) to be set through GUC.
-
- 27 Jun, 2001 1 commit
-
-
Tom Lane authored
do anything yet, but it has the necessary connections to initialization and so forth. Make some gestures towards allowing number of blocks in a relation to be BlockNumber, ie, unsigned int, rather than signed int. (I doubt I got all the places that are sloppy about it, yet.) On the way, replace the hardwired NLOCKS_PER_XACT fudge factor with a GUC variable.
-
- 18 Jun, 2001 1 commit
-
-
Bruce Momjian authored
functions to clear date cache. Allow regression tests to pass when timezone set.
-
- 07 May, 2001 1 commit
-
-
Bruce Momjian authored
-
- 16 Mar, 2001 1 commit
-
-
Tom Lane authored
O_SYNC, or O_DSYNC (as available on a given platform). Add GUC parameter to control sync method. Also, add defense to XLogWrite to prevent it from going nuts if passed a target write position that's past the end of the buffers so far filled by XLogInsert.
-
- 13 Mar, 2001 1 commit
-
-
Tom Lane authored
* Store two past checkpoint locations, not just one, in pg_control. On startup, we fall back to the older checkpoint if the newer one is unreadable. Also, a physical copy of the newest checkpoint record is kept in pg_control for possible use in disaster recovery (ie, complete loss of pg_xlog). Also add a version number for pg_control itself. Remove archdir from pg_control; it ought to be a GUC parameter, not a special case (not that it's implemented yet anyway). * Suppress successive checkpoint records when nothing has been entered in the WAL log since the last one. This is not so much to avoid I/O as to make it actually useful to keep track of the last two checkpoints. If the things are right next to each other then there's not a lot of redundancy gained... * Change CRC scheme to a true 64-bit CRC, not a pair of 32-bit CRCs on alternate bytes. Polynomial borrowed from ECMA DLT1 standard. * Fix XLOG record length handling so that it will work at BLCKSZ = 32k. * Change XID allocation to work more like OID allocation. (This is of dubious necessity, but I think it's a good idea anyway.) * Fix a number of minor bugs, such as off-by-one logic for XLOG file wraparound at the 4 gig mark. * Add documentation and clean up some coding infelicities; move file format declarations out to include files where planned contrib utilities can get at them. * Checkpoint will now occur every CHECKPOINT_SEGMENTS log segments or every CHECKPOINT_TIMEOUT seconds, whichever comes first. It is also possible to force a checkpoint by sending SIGUSR1 to the postmaster (undocumented feature...) * Defend against kill -9 postmaster by storing shmem block's key and ID in postmaster.pid lockfile, and checking at startup to ensure that no processes are still connected to old shmem block (if it still exists). * Switch backends to accept SIGQUIT rather than SIGUSR1 for emergency stop, for symmetry with postmaster and xlog utilities. Clean up signal handling in bootstrap.c so that xlog utilities launched by postmaster will react to signals better. * Standalone bootstrap now grabs lockfile in target directory, as added insurance against running it in parallel with live postmaster.
-
- 26 Feb, 2001 1 commit
-
-
Tom Lane authored
only if at least N other backends currently have open transactions. This is not a great deal of intelligence about whether a delay might be profitable ... but it beats no intelligence at all. Note that the default COMMIT_DELAY is still zero --- this new code does nothing unless that setting is changed. Also, mark ENABLEFSYNC as a system-wide setting. It's no longer safe to allow that to be set per-backend, since we may be relying on some other backend's fsync to have synced the WAL log.
-
- 18 Feb, 2001 1 commit
-
-
Tom Lane authored
-
- 24 Jan, 2001 4 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Bruce Momjian authored
-
- 03 Dec, 2000 1 commit
-
-
Peter Eisentraut authored
-