Alvaro Herrera wrote:
Here is another patch for autovacuum:
...
- Xid-wraparound VACUUM is now FULL without ANALYZE
Am I right in my assumption that this VACUUM FULL can happen for any
database, not just a template database?
I think this is a bad idea. Vacuum full is not an option for
-Original Message-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]
Sent: 01 August 2005 03:26
To: Dave Page
Cc: PostgreSQL-patches
Subject: Re: [HACKERS] For review: Server instrumentation patch
Dave Page wrote:
[Resent as the list seems to have rejected yesterdays attempt]
Am Montag, 25. Juli 2005 18:31 schrieb Tom Lane:
Bruce Momjian pgman@candle.pha.pa.us writes:
The new syntax for this command is CREATE/ALTER DATABASE/USER:
| MAX CONNECTIONS Iconst
This adds 'max' as a keyword, though at a fairly unreserved level, I
think. Should we
The attached patch updates the thread test program to run stand-alone on
Windows. The test itself is bypassed in configure as discussed, and
libpq has been updated appropriately to allow it to build in thread-safe
mode.
To apply, apply the patch as normal, then rename
On Mon, Aug 01, 2005 at 09:55:11AM +0200, Michael Paesold wrote:
Alvaro Herrera wrote:
Here is another patch for autovacuum:
...
- Xid-wraparound VACUUM is now FULL without ANALYZE
Am I right in my assumption that this VACUUM FULL can happen for any
database, not just a template
Dave Page wrote:
-Original Message-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]
Sent: 01 August 2005 03:26
To: Dave Page
Cc: PostgreSQL-patches
Subject: Re: [HACKERS] For review: Server instrumentation patch
Dave Page wrote:
[Resent as the list seems to have rejected
-Original Message-
From: Andreas Pflug [mailto:[EMAIL PROTECTED]
Sent: 01 August 2005 14:47
To: Dave Page
Cc: Bruce Momjian; PostgreSQL-patches
Subject: Re: [PATCHES] [HACKERS] For review: Server
instrumentation patch
Dave Page wrote:
-Original Message-
Alvaro Herrera [EMAIL PROTECTED] writes:
- Xid-wraparound VACUUM is now FULL without ANALYZE
Am I right in my assumption that this VACUUM FULL can happen for any
database, not just a template database?
Ah, right. I think it would be OK if we made it FULL only for
datallowcon=false
Dave Page wrote:
pg_dir_ls isn't necessary for reading the logfiles;
pg_logdir_ls will do
this.
Err, yes, sorry - that was a thinko.
The list isn't complete. pgadmin uses these three functions for logfile
tracking:
- pg_logdir_ls to list logfiles
- pg_file_length to check for changes
Peter Eisentraut wrote:
Am Montag, 25. Juli 2005 18:31 schrieb Tom Lane:
Bruce Momjian pgman@candle.pha.pa.us writes:
The new syntax for this command is CREATE/ALTER DATABASE/USER:
| MAX CONNECTIONS Iconst
This adds 'max' as a keyword, though at a fairly unreserved
An updated version of your patch has been applied and will be in 8.1. Thanks.
---
pgman wrote:
I have worked over your patch and I think it is ready for application.
I changed the syntax to CONNECTION LIMIT, which
-Original Message-
From: Andreas Pflug [mailto:[EMAIL PROTECTED]
Sent: 01 August 2005 15:05
To: Dave Page
Cc: Bruce Momjian; PostgreSQL-patches
Subject: Re: [PATCHES] [HACKERS] For review: Server
instrumentation patch
Dave Page wrote:
pg_dir_ls isn't necessary for
Bruce Momjian pgman@candle.pha.pa.us writes:
Peter Eisentraut wrote:
Would this not work in the context of the general user-specific ALTER USER
...
SET something = something?
No because it isn't a GUC variable, it is per-user/db value. We could
have used that syntax, but it might confuse
--On Donnerstag, Juli 28, 2005 23:12:37 -0400 Bruce Momjian
pgman@candle.pha.pa.us wrote:
Here is an updated version of your patch. Would you supply SGML
documentation updates to match the code changes? Thanks.
Here's my first shot on this. Let me know if there's somenthing missing or
Bernd Helmle [EMAIL PROTECTED] writes:
Here is an updated version of your patch. Would you supply SGML
documentation updates to match the code changes? Thanks.
Here's my first shot on this.
Applied with additional minor editing.
regards, tom lane
Karel Zak [EMAIL PROTECTED] writes:
This is new version of SELECT FOR UPDATE NOWAIT patch.
Applied with revisions.
regards, tom lane
---(end of broadcast)---
TIP 6: explain analyze is your friend
o pgp_mpi_free: Accept NULLs
o pgp_mpi_cksum: result should be 16bit
o Remove function name from error messages - to be similar to other
SQL functions, and it does not match anyway the called function
o remove couple junk lines
Index: pgsql/contrib/pgcrypto/pgp-mpi.c
I was bit hasty making the random exponent 'k' a prime. Further researh
shows that Elgamal encryption has no specific needs in respect to k,
any random number is fine.
It is bit different for signing, there it needs to be 'relatively prime'
to p - 1, that means GCD(k, p-1) == 1, which is also a
o Tom stuck a CVS id into file. I doubt the usefulness of it,
but if it needs to be in the file then rather at the end.
Also tag it as comment for asciidoc.
o Mention bytea vs. text difference
o Couple clarifications
Index: pgsql/contrib/pgcrypto/README.pgcrypto
The SHLIB section was copy-pasted from somewhere and contains
several unnecessary libs. This cleans it up a bit.
-lcrypt
we don't use system crypt()
-lssl, -lssleay32
no SSL here
-lz in win32 section
already added on previous line
-ldes
The chance anybody has it is pretty low.
o Support for RSA encryption
o Big reorg to better separate generic and algorithm-specific code.
o Regression tests for RSA.
Index: pgsql/contrib/pgcrypto/pgp-mpi-openssl.c
===
*** pgsql.orig/contrib/pgcrypto/pgp-mpi-openssl.c
It is already disabled in Makefile, remove code too.
Index: pgsql/contrib/pgcrypto/px-crypt.c
===
*** pgsql.orig/contrib/pgcrypto/px-crypt.c
--- pgsql/contrib/pgcrypto/px-crypt.c
***
*** 35,42
#include px-crypt.h
Alon Goldshuv [EMAIL PROTECTED] writes:
This patch appears to reverse out the most recent committed changes in
copy.c.
Which changes do you refer to? I thought I accommodated all the recent
changes (I recall some changes to the tupletable/tupleslot interface, HEADER
in cvs, and hex escapes
Rocco Altier [EMAIL PROTECTED] writes:
Here is a backport of patches to get AIX to work on 8.0.
Basically, it's the changes to :
backend/Makefile - redo the linking of the SUBSYS objects
contrib/cube - pick up -lm
port/getopt_long.c - fix include files (might want to think about other
files
24 matches
Mail list logo
