- 12 Sep, 2001 1 commit
-
-
Peter Eisentraut authored
max_locks_per_xact.
-
- 09 Sep, 2001 1 commit
-
-
Peter Eisentraut authored
-
- 07 Sep, 2001 1 commit
-
-
Tom Lane authored
max_connections.
-
- 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.
-
- 09 Aug, 2001 1 commit
-
-
Peter Eisentraut authored
-
- 15 Jul, 2001 1 commit
-
-
Peter Eisentraut authored
accordingly.
-
- 30 Jun, 2001 2 commits
-
-
Peter Eisentraut authored
characteristics) to be set through GUC.
-
D'Arcy J.M. Cain authored
I just finished changing the GENERIC files and the options(4) man page on NetBSD to make this clearer.
-
- 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.
-
- 23 Jun, 2001 1 commit
-
-
Peter Eisentraut authored
-
- 18 Jun, 2001 1 commit
-
-
Bruce Momjian authored
functions to clear date cache. Allow regression tests to pass when timezone set.
-
- 17 May, 2001 1 commit
-
-
Peter Eisentraut authored
library extension.
-
- 12 May, 2001 1 commit
-
-
Peter Eisentraut authored
-
- 08 May, 2001 1 commit
-
-
Bruce Momjian authored
-
- 07 May, 2001 1 commit
-
-
Bruce Momjian authored
-
- 04 May, 2001 2 commits
-
-
Tom Lane authored
configuration parameters in chapter 3.
-
Bruce Momjian authored
-
- 03 May, 2001 1 commit
-
-
Bruce Momjian authored
-
- 02 May, 2001 1 commit
-
-
Bruce Momjian authored
-
- 01 May, 2001 1 commit
-
-
Tom Lane authored
-
- 24 Mar, 2001 1 commit
-
-
Tom Lane 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.
-
- 18 Feb, 2001 1 commit
-
-
Tom Lane authored
-
- 16 Feb, 2001 3 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Bruce Momjian authored
-
- 15 Feb, 2001 1 commit
-
-
Tom Lane authored
-
- 10 Feb, 2001 1 commit
-
-
Peter Eisentraut authored
-
- 09 Feb, 2001 1 commit
-
-
Peter Eisentraut authored
apparently when the content is long enough to require line breaks.
-
- 24 Jan, 2001 2 commits
-
-
Peter Eisentraut authored
-
Bruce Momjian authored
privkey.pem cert.pem.pw" if you just use "privkey.pem" in the following openssl command (e.g. openssl rsa -in privkey.pem -out cert.pem". But there is nothing wrong with it as it is now, as far as I can see. //Magnus
-
- 08 Jan, 2001 1 commit
-
-
Peter Eisentraut authored
-
- 30 Dec, 2000 1 commit
-
-
Peter Eisentraut authored
-
- 22 Dec, 2000 1 commit
-
-
Tom Lane authored
-
- 21 Dec, 2000 1 commit
-
-
Bruce Momjian authored
>mv privkey.pem cert.pem.pw >openssl rsa -in cert.pem.pw -out cert.pem (this removes the password) >openssl req -x509 -in cert.req -text -key cert.pem -out cert.cert then cp cert.pem $PGDATA/server.key cp cert.cert $PGDATA/server.crt Thank you; this works. Oliver Elphick
-
- 17 Dec, 2000 1 commit
-
-
Peter Eisentraut authored
-
- 03 Dec, 2000 1 commit
-
-
Peter Eisentraut authored
-
- 30 Nov, 2000 1 commit
-
-
Tom Lane authored
I hope all the dust has settled out now ...
-
- 25 Nov, 2000 1 commit
-
-
Tom Lane authored
re-adopt these settings at every postmaster or standalone-backend startup. This should fix problems with indexes becoming corrupt due to failure to provide consistent locale environment for postmaster at all times. Also, refuse to start up a non-locale-enabled compilation in a database originally initdb'd with a non-C locale. Suppress LIKE index optimization if locale is not "C" or "POSIX" (are there any other locales where it's safe?). Issue NOTICE during initdb if selected locale disables LIKE optimization.
-