[HACKERS] Recent buildfarm failures involving statement_timeout

2008-04-27 Thread Tom Lane
The buildfarm has shown several intermittent failures recently: http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=herondt=2008-04-20%2000:06:01 http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=cobradt=2008-04-26%2004:15:02

Re: [HACKERS] we don't have a bugzilla

2008-04-27 Thread Shane Ambler
Andrew Sullivan wrote: On Sat, Apr 26, 2008 at 08:54:46AM -0700, Joshua D. Drake wrote: How would he know to search at the archives? * There is no archives signature at the bottom of -hackers lists Maybe because there's a perfectly functional archive link in the mail headers? And because

Re: [HACKERS] Recent buildfarm failures involving statement_timeout

2008-04-27 Thread Gregory Stark
Tom Lane [EMAIL PROTECTED] writes: Another theory is that we broke something recently, but I see no obvious candidates in the CVS logs --- and I've spent the evening running 488 cycles of the parallel regression tests here, with no error. It looks to me like a psql bug rather than a server

Re: [HACKERS] Recent buildfarm failures involving statement_timeout

2008-04-27 Thread Andrew Dunstan
Tom Lane wrote: The buildfarm has shown several intermittent failures recently: http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=herondt=2008-04-20%2000:06:01 http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=cobradt=2008-04-26%2004:15:02

Re: [HACKERS] Recent buildfarm failures involving statement_timeout

2008-04-27 Thread Tom Lane
Gregory Stark [EMAIL PROTECTED] writes: Tom Lane [EMAIL PROTECTED] writes: Another theory is that we broke something recently, but I see no obvious candidates in the CVS logs --- and I've spent the evening running 488 cycles of the parallel regression tests here, with no error. It looks to

Re: [HACKERS] Recent buildfarm failures involving statement_timeout

2008-04-27 Thread Tom Lane
Andrew Dunstan [EMAIL PROTECTED] writes: pgbfprod=# select sysname, snapshot from build_status_log where branch = 'HEAD' and log_stage = 'check.log' and log_text ~ $$\+ ERROR: canceling statement due to statement timeout$$; sysname | snapshot -+-

Re: [HACKERS] Recent buildfarm failures involving statement_timeout

2008-04-27 Thread Andrew Dunstan
Tom Lane wrote: Andrew Dunstan [EMAIL PROTECTED] writes: pgbfprod=# select sysname, snapshot from build_status_log where branch = 'HEAD' and log_stage = 'check.log' and log_text ~ $$\+ ERROR: canceling statement due to statement timeout$$; sysname | snapshot

Re: [HACKERS] Invalid to_date patterns (was: [PATCHES] [GENERAL] ISO week dates)

2008-04-27 Thread Brendan Jurd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm picking this one up again, since my refactor of formatting.c has been applied, and I seem to be done playing with psql for the time being =) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.7 (GNU/Linux) Comment: http://getfiregpg.org

Re: [HACKERS] Proposed patch - psql wraps at window width

2008-04-27 Thread Bryce Nesbitt
Tom Lane wrote: Bruce Momjian [EMAIL PROTECTED] writes: I don't see that behavior here on Ubuntu 7.10: $ COLUMNNS=120 ls -C |cat archive cdinitrd lost+found proc srv usr basement.usr dev initrd.img media root sys var bin

[HACKERS] quirk using 'ltree' module: paths ending with a dot result in cryptic error message

2008-04-27 Thread Jeff MacDonald
greetings, I am using opensuse 10.3, and postgresql-contrib-8.2.6-0.1 which has the ltree contrib bundled with it. I have found that if I do a search with a path that ends in a . (dot), the error message I get in my logs is something like unexpected end of line or some such, which imo doesn't