-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 21 Feb 2008 13:38:50 -0500 Tom Lane <[EMAIL PROTECTED]> wrote:
> "Joshua D. Drake" <[EMAIL PROTECTED]> writes: > > In one fell swoop I could crash *any* postgresql database running > > 8.2.6 or below (I haven't tested this on 8.3). > > Uh, I seem to have missed where the crash was in this example? I wasn't willing to dump my machine. However I could: A. Exhaust all resources B. Fill up my hard drive C. Render the application unusable for other users D. Lock out DDL operations by beginning a transaction E. Cause xid wrap around by leaving an open transaction idle and thus force a shutdown of postgresql Although you are correct, I should not use the term crash. The above would not "crash" PostgreSQL, (although Linux might kill it). It does however have the ability to wreak havoc on the environment. Sincerely, Joshua D. Drake - -- The PostgreSQL Company since 1997: http://www.commandprompt.com/ PostgreSQL Community Conference: http://www.postgresqlconference.org/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL SPI Liaison | SPI Director | PostgreSQL political pundit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHvcb2ATb/zqfZUUQRAlgBAJ4y2tFWXJgGwJD95kcg91wIVCk6jwCfbVZe 91Q4CkmzbM1ctM0GX86Kdeg= =7KDu -----END PGP SIGNATURE----- ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
