PgSql

[HACKERS] pg_read_file() and non-ascii input file
pg_read_file() takes byte-offset and length as arguments, but we don't check the result text with pg_verify_mbstr(). Should pg_read_file() return bytea instead of text or adding some codes to verify the input? Only superusers are allowed to use the function, but it is still dangerous. If we leave the result in... 27 Oct 2009 22:39

xpath_table equivalent
Chris Graner wrote: Hello, I've been reading over the documentation to find an alternative to the deprecated xpath_table functionality. I think it may be a possibility but I'm not seeing a clear alternative. Thanks, Chris Graner The standard is XMLTABLE and is implemented by both db2 ... 21 Nov 2009 12:32

Extraneous newlines in logfile from vacuumdb
Tim Landscheidt <tim(a)tim-landscheidt.de> writes: log file entries from running vacuumdb are "double-spaced", as vacuumdb ends the commands with ";\n" (cf. attached mini- patch). Is there a deeper meaning in that, or could it be trimmed? There are a LOT of clients that tend to send queries with trailing ... 27 Oct 2009 18:09

Endgame for all those SELECT FOR UPDATE changes: fix plan node order
On Oct 25, 2009, at 10:34 PM, Tom Lane <tgl(a)sss.pgh.pa.us> wrote: Now that we've got a hopefully-non-broken implementation of SELECT FOR UPDATE locking as a plan node, we can finally contemplate fixing two misbehaviors that are called out on the SELECT reference page: It is possible for a SELECT com... 27 Oct 2009 18:09

[HACKERS] License clarification: BSD vs MIT
Background info: Fedora/Red Hat folks (not Tom...) changed license in PostgreSQL spec file from BSD to MIT with the following notice: # PG considers their license to be simplified BSD, but it's more nearly MIT Our license wording fits perfectly to MIT, if I'm not wrong. However, we always advertise ourselves... 25 Oct 2009 18:43

(WIP) VACUUM REWRITE - CLUSTER by ctid
Itagaki Takahiro wrote: I'm working on alternative version of VACUUM FULL, which is like CLUSTER but sort tuples in ctid order without index. The original discussion is here: [HACKERS] Feedback on getting rid of VACUUM FULL http://archives.postgresql.org/pgsql-hackers/2009-09/msg01047.php ... 25 Oct 2009 23:08

BUG #5065: pg_ctl start fails as administrator,with "could not locate matching postgres executable"
Magnus Hagander wrote: From a quick look, it looks fine to me. I don't have time to do a complete check right now, but I'll do that as soon as I can and then commit it - unless people feel it's more urgent than maybe a week worst case, in which case someone else has to pick it up :-) Are we going to do... 21 Oct 2009 10:23

alpha1 bundled -- please verify
On Wed, 2009-08-19 at 19:11 +0200, Stefan Kaltenbrunner wrote: correct - svr1 has bison 1.875 and flex 2.5.35 (for the -HEAD builds) and flex 2.5.4 for the back branches. Where? In which directories? -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscri... 20 Oct 2009 20:07

ProcessUtility_hook
Itagaki Takahiro escreveu: We can hook SELECT, INSERT, UPDATE and DELETE with ExecutorXxx_hooks, but there is no way to hook DDL commands. Can I submit a patch to add ProcessUtility_hook? +1. Hey, I was thinking about that yesterday. ;) pg_stat_statements module also handle DDL commands as same as no... 15 Dec 2009 15:36

UTF8 with BOM support in psql
Itagaki Takahiro wrote: UTF8 encoding text files with BOM (Byte Order Mark) are commonly used in Windows, though BOM was designed for UTF16 text originally. However, psql cannot read such format even if we set client encoding to UTF8. Is it worth supporting those format in psql? When psql opens a fil... 21 Nov 2009 19:15