Re: [HACKERS] [COMMITTERS] pgsql: /home/peter/commit-msg

2009-11-20 Thread Kris Jurka
On Fri, 20 Nov 2009, Magnus Hagander wrote: I've cleaned up the git repo, and re-enabled the mirror script. From what I can tell it works fine. In theory you will need to use force mode if you pulled the broken commit that was removed (the one with the wrong message), but it seems this is not

Re: [HACKERS] [COMMITTERS] pgsql: /home/peter/commit-msg

2009-11-20 Thread Heikki Linnakangas
Kris Jurka wrote: > On Fri, 20 Nov 2009, Magnus Hagander wrote: > >> I've cleaned up the git repo, and re-enabled the mirror script. From >> what I can tell it works fine. In theory you will need to use force >> mode if you pulled the broken commit that was removed (the one with >> the wrong messa

Re: [HACKERS] [COMMITTERS] pgsql: /home/peter/commit-msg

2009-11-20 Thread Robert Haas
On Fri, Nov 20, 2009 at 2:44 PM, Heikki Linnakangas wrote: > Kris Jurka wrote: >> On Fri, 20 Nov 2009, Magnus Hagander wrote: >> >>> I've cleaned up the git repo, and re-enabled the mirror script. From >>> what I can tell it works fine. In theory you will need to use force >>> mode if you pulled t

[COMMITTERS] pgsql: Add a WHEN clause to CREATE TRIGGER, allowing a boolean

2009-11-20 Thread Tom Lane
Log Message: --- Add a WHEN clause to CREATE TRIGGER, allowing a boolean expression to be checked to determine whether the trigger should be fired. For BEFORE triggers this is mostly a matter of spec compliance; but for AFTER triggers it can provide a noticeable performance improvement, si

[COMMITTERS] pgsql: Fix display and dumping of UPDATE OR TRUNCATE triggers (a bizarre

2009-11-20 Thread Tom Lane
Log Message: --- Fix display and dumping of UPDATE OR TRUNCATE triggers (a bizarre combination maybe, but we should get it right). Bug noted while reviewing TRIGGER WHEN patch. Already fixed in HEAD. Tags: REL8_4_STABLE Modified Files: -- pgsql/src/backend/utils/adt

[COMMITTERS] libpqtypes - libpqtypes: Fixed bug in pqt_allowsptr, it was returning

2009-11-20 Thread User Achernow
Log Message: --- Fixed bug in pqt_allowsptr, it was returning FALSE for types registered w/o a schema. It now returns TRUE which is the correct behavior. Modified Files: -- libpqtypes/src: handler.c (r1.19 -> r1.20) (http://cvs.pgfoundry.org/cgi-bin/cvswe

[COMMITTERS] libpqtypes - libpqtypes: Update ChnageLog

2009-11-20 Thread User Achernow
Log Message: --- Update ChnageLog Modified Files: -- libpqtypes: ChangeLog (r1.44 -> r1.45) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/libpqtypes/libpqtypes/ChangeLog?r1=1.44&r2=1.45) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresq

Re: [HACKERS] [COMMITTERS] pgsql: /home/peter/commit-msg

2009-11-20 Thread Magnus Hagander
2009/11/20 Heikki Linnakangas : > Kris Jurka wrote: >> On Fri, 20 Nov 2009, Magnus Hagander wrote: >> >>> I've cleaned up the git repo, and re-enabled the mirror script. From >>> what I can tell it works fine. In theory you will need to use force >>> mode if you pulled the broken commit that was re

[COMMITTERS] pgsql: Refactor ecpg grammar so that it uses the core grammar's

2009-11-20 Thread Tom Lane
Log Message: --- Refactor ecpg grammar so that it uses the core grammar's unreserved_keyword list, minus a few specific words that have to be treated specially. This replaces a hard-wired list of keywords that would have needed manual maintenance, and was not getting it. The 8.4 coding wa

[COMMITTERS] pgsql: Refactor ecpg grammar so that it uses the core grammar's

2009-11-20 Thread Tom Lane
Log Message: --- Refactor ecpg grammar so that it uses the core grammar's unreserved_keyword list, minus a few specific words that have to be treated specially. This replaces a hard-wired list of keywords that would have needed manual maintenance, and was not getting it. The 8.4 coding wa