Zach Irmen wrote:
Bruce Momjian wrote:
Yes, seems like that will be required. Please use my attached version
to make the adjustments.
Ok. Adjustments made. All psql commands should be handled.
Zach Irmen wrote:
And finally, I was wondering if arguments with leading pipes
Patch applied. Thanks.
---
Zach Irmen wrote:
Bruce Momjian wrote:
Yes, seems like that will be required. Please use my attached version
to make the adjustments.
Ok. Adjustments made. All psql commands should be
Patch applied. Thanks.
---
Zach Irmen wrote:
As far as I can tell, the file argument for \w is required;
this contradicts what \? says for it (namely that it's optional).
A patch follows to fix this if it really is an
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
Claudio Natoli wrote:
For application
Tom Lane wrote:
Jan Wieck [EMAIL PROTECTED] writes:
Something after 2003/11/20 enhanced the query cancel handling. Namely,
CVS tip now responds to a query cancel with a postmaster restart
canceling all queries. Could the fork/exec stuff be responsible for this?
Whoever changed this:
Tom Lane wrote:
Jan Wieck [EMAIL PROTECTED] writes:
Something after 2003/11/20 enhanced the query cancel handling. Namely,
CVS tip now responds to a query cancel with a postmaster restart
canceling all queries. Could the fork/exec stuff be responsible for this?
Whoever changed this:
Done and attached.
---
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Claudio specified the attached fix, which I have applied (this time).
The ereport must vanish back into its black hole, also.
When pg_ctl is used to start the postmaster without the -w flag, it says
postmaster successfully started
when in fact it should be postmaster starting because it hasn't
started yet, or at least isn't accepting connections yet. A wait for
start says:
waiting for postmaster to
