Re: [COMMITTERS] pgsql: Don't try to compile SSL CRL support if local SSL installation

2006-05-04 Thread Tom Lane
Kris Jurka <[EMAIL PROTECTED]> writes: > On Thu, 4 May 2006, Tom Lane wrote: >> Don't try to compile SSL CRL support if local SSL installation hasn't >> got it. Per buildfarm failure on 'canary'. > It seems a little bit dangerous to just not check the CRL without so much > as a warning message.

Re: [COMMITTERS] pgsql: Don't try to compile SSL CRL support if

2006-05-04 Thread Kris Jurka
On Thu, 4 May 2006, Tom Lane wrote: Log Message: --- Don't try to compile SSL CRL support if local SSL installation hasn't got it. Per buildfarm failure on 'canary'. It seems a little bit dangerous to just not check the CRL without so much as a warning message. CRL support came a

[COMMITTERS] pgsql: Don't try to compile SSL CRL support if local SSL installation

2006-05-04 Thread Tom Lane
Log Message: --- Don't try to compile SSL CRL support if local SSL installation hasn't got it. Per buildfarm failure on 'canary'. Modified Files: -- pgsql/src/backend/libpq: be-secure.c (r1.66 -> r1.67) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src

[COMMITTERS] pgsql: Code review for contrib/pg_freespacemap.

2006-05-04 Thread Tom Lane
Log Message: --- Code review for contrib/pg_freespacemap. Add a storedpages column to pg_freespacemap_relations --- while one could theoretically get that number by counting rows in pg_freespacemap_pages, it's surely the hard way to do it. Avoid expensive and inconvenient conversion to an

[COMMITTERS] pgsql: Simplify relcache startup sequence.

2006-05-04 Thread Tom Lane
Log Message: --- Simplify relcache startup sequence. With the new design of InitPostgres it's not necessary to have three separate calls anymore. This patch also fixes things so we don't try to read pg_internal.init until after we've obtained lock on the target database; which was fairly

[COMMITTERS] pgsql: Rethink the locking mechanisms used for CREATE/DROP/RENAME

2006-05-04 Thread Tom Lane
Log Message: --- Rethink the locking mechanisms used for CREATE/DROP/RENAME DATABASE. The former approach used ExclusiveLock on pg_database, which being a cluster-wide lock meant only one of these operations could proceed at a time; worse, it also blocked all incoming connections in Reverif

[COMMITTERS] npgsql - Npgsql: 2006-05-04 Francisco Figueiredo Jr.

2006-05-04 Thread User Fxjr
Log Message: --- 2006-05-04 Francisco Figueiredo Jr. <[EMAIL PROTECTED]> * NpgsqlCommand.cs: return count for fetch and move, too, patch from Federico Di Gregorio (fog at initd dot org). Changed UpdateOutputParameters to use FieldIndex which now doesn't throw exceptions when n