[COMMITTERS] pgsql: Provide a parenthesized-options syntax for VACUUM, analogous to

2009-11-16 Thread Tom Lane
Log Message: --- Provide a parenthesized-options syntax for VACUUM, analogous to that recently adopted for EXPLAIN. This will allow additional options to be implemented in future without having to make them fully-reserved keywords. The old syntax remains available for existing options, ho

[COMMITTERS] pgsql: While doing the final setrefs.c pass over a plan tree, try to

2009-11-16 Thread Tom Lane
Log Message: --- While doing the final setrefs.c pass over a plan tree, try to match up non-Var sort/group expressions using ressortgroupref labels instead of depending entirely on equal()-ity of the upper node's tlist expressions to the lower node's. This avoids emitting the wrong outputs

[COMMITTERS] pgsql: While doing the final setrefs.c pass over a plan tree, try to

2009-11-16 Thread Tom Lane
Log Message: --- While doing the final setrefs.c pass over a plan tree, try to match up non-Var sort/group expressions using ressortgroupref labels instead of depending entirely on equal()-ity of the upper node's tlist expressions to the lower node's. This avoids emitting the wrong outputs

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

2009-11-16 Thread Peter Eisentraut
On mån, 2009-11-16 at 10:05 -0500, Tom Lane wrote: > Heikki Linnakangas writes: > > Magnus Hagander wrote: > >> On Mon, Nov 16, 2009 at 08:29, David Fetter wrote: > >>> On Mon, Nov 16, 2009 at 06:56:54AM +0200, Peter Eisentraut wrote: > Yeah, sorry guys. I fixed the CVS log message now. >

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

2009-11-16 Thread Tom Lane
Heikki Linnakangas writes: > Magnus Hagander wrote: >> On Mon, Nov 16, 2009 at 08:29, David Fetter wrote: >>> On Mon, Nov 16, 2009 at 06:56:54AM +0200, Peter Eisentraut wrote: Yeah, sorry guys. I fixed the CVS log message now. >> So it's not only not strange, I'm very happy it didn't pull

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

2009-11-16 Thread Peter Eisentraut
On sön, 2009-11-15 at 17:09 -0500, Tom Lane wrote: > David Fetter writes: > > On Sun, Nov 15, 2009 at 10:09:14AM -0500, Andrew Dunstan wrote: > >> Peter Eisentraut wrote: > >>> /home/peter/commit-msg > >> er, what? > > I'm suspecting a misfired script somewhere. > > No doubt "cvs commit -m ~/comm

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

2009-11-16 Thread Heikki Linnakangas
Heikki Linnakangas wrote: > So we could rewrite the git history too, and I think it would be quite > nice to have the right commit message there as well. But I don't care > enough to volunteer to do the legwork. If we are going to do it, we > should do it as soon as possible, while we're only a cou

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

2009-11-16 Thread Magnus Hagander
On Mon, Nov 16, 2009 at 09:05, Heikki Linnakangas wrote: > Magnus Hagander wrote: >> On Mon, Nov 16, 2009 at 08:29, David Fetter wrote: >>> On Mon, Nov 16, 2009 at 06:56:54AM +0200, Peter Eisentraut wrote: Yeah, sorry guys.  I fixed the CVS log message now. >>> Strangely, the git repo still

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

2009-11-16 Thread Heikki Linnakangas
Magnus Hagander wrote: > On Mon, Nov 16, 2009 at 08:29, David Fetter wrote: >> On Mon, Nov 16, 2009 at 06:56:54AM +0200, Peter Eisentraut wrote: >>> Yeah, sorry guys. I fixed the CVS log message now. >> Strangely, the git repo still shows the old message. For the record, >> there's the new one: