PgSql

[HACKERS] pgindent cleanup
Following up Tom's complaint about behaviour of pgindent, I have been wrestling with it a bit. I noticed several things. First awk on my box spits out fairly useless warnings about regular expressions containing a literal '\*'. These warnings are silenced by replacing those with '[*]', which should have the ... 3 Apr 2010 12:36

message clarifications
On Sat, 2010-04-03 at 11:00 +0300, Peter Eisentraut wrote: The following messages from the postgres catalog either appear to be internal errors that should be marked differently, or they are in my estimation unintelligible to users and should be rephrased. OK, will look. -- Simon Riggs www.2... 6 Apr 2010 13:02

pgindent bizarreness
Tom Lane wrote: Why has pgindent decided to screw up all the FD_SET calls in our code? See for example http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/pgstat.c.diff?r1=1.188;r2=1.189 This appears to be due to this on mingw: /mingw/include/winsock.h:typedef st... 4 Apr 2010 23:40

[RFC] nodeToString format and exporting the SQL parser
Michael Tharp <gxti(a)partiallystapled.com> writes: Due to popular demand on #postgresql (by which I mean David Fetter), I have been spending a little time making the internal SQL parser available to clients via a C-language SQL function. The function itself is extremely simple: just a wrapper around a cal... 24 Apr 2010 21:38

[HACKERS] [RFC] nodeToString format and exporting the SQL parser
Most Esteemed Hackers: Due to popular demand on #postgresql (by which I mean David Fetter), I have been spending a little time making the internal SQL parser available to clients via a C-language SQL function. The function itself is extremely simple: just a wrapper around a call to raw_parser followed by nod... 2 Apr 2010 17:04

[HACKERS] inlining SQL functions
Hi, Is there a reason why only a table free SQL functions are allowed to be inlined ? I wonder why a simple SQL function containing only a SELECT * FROM table can't be expanded inline ? Is there an interest in expanding the class of SQL functions that can be inlined ? Thanks, -- Alexey Klyukin http://... 2 Apr 2010 13:44

pgstattuple does not contain CHECK_FOR_INTERRUPTS()
Tatsuhito Kasahara <kasahara.tatsuhito(a)oss.ntt.co.jp> writes: pgstattuple (and pgstatindex) does not contain CHECK_FOR_INTERRUPTS(). Therefore, we can not stop pgstattuple() by using the signal while a large table is processed. Here is the patch to solve it. Seems to be a good idea --- will apply. Tha... 2 Apr 2010 12:37

[HACKERS] pgindent bizarreness
Why has pgindent decided to screw up all the FD_SET calls in our code? See for example http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/pgstat.c.diff?r1=1.188;r2=1.189 regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subsc... 2 Apr 2010 11:30

[HACKERS] pgstattuple does not contain CHECK_FOR_INTERRUPTS()
Hi, pgstattuple (and pgstatindex) does not contain CHECK_FOR_INTERRUPTS(). Therefore, we can not stop pgstattuple() by using the signal while a large table is processed. Here is the patch to solve it. Best regards, -- NTT OSS Center Tatsuhito Kasahara ... 2 Apr 2010 07:06

[HACKERS] Compile fail, alpha5 & gcc 4.3.3 in elog.c
Guys, Hmmm. I appear to have had a compile error with that alpha5 tarball, in elog.c. No special options on compile, except an alternate directory and port. Ubunutu 9.10 server GCC 4.3.3 Tries both: ../configure --with-pgport=5490 --prefix=/usr/local/pgsql/9.0/ and: ../configure --with-pgport=5490 --pre... 2 Apr 2010 01:44