PgSql

[HACKERS] function side effects
Hi, I'm wondering if we could detect a funcion has a side effect, i.e. does a write to database. This is neccessary for pgpool to decide if a qeury should to be sent to all of databases or not. If a query includes functions which do writes to database, it should send the query to all of databases, otherwise the ... 22 Feb 2010 23:09

updated hstore patch
Tom Lane wrote: "David E. Wheeler" <david(a)kineticode.com> writes: On Sep 20, 2009, at 8:43 AM, Tom Lane wrote: Yeah, this is a long-standing generic issue, and not really hstore's problem to fix. So then does there need to be some documentation for how to deal with this, for those do... 22 Feb 2010 22:03

commented out para in docs
Andrew Dunstan wrote: We have this para in the CREATE TABLE docs, commented out, as shown. It seems to have been like that for a long time (see <http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/create_table.sgml?annotate=1.48>). Surely we should either include it or remove it. H... 22 Feb 2010 19:49

tie user processes to postmaster was:(Re: [HACKERS] scheduler in core)
Jaime Casanova wrote: if we can do this, how should it work? Simon said: """ Yes, I think so. Rough design... integrated_user_processes = 'x, y, z' would run x(), y() and z() in their own processes. These would execute after startup, or at consistent point in recovery. The code for these ... 22 Feb 2010 14:09

[HACKERS] tie user processes to postmaster was:(Re: [HACKERS] scheduler in core)
On Mon, Feb 22, 2010 at 1:18 PM, Heikki Linnakangas <heikki.linnakangas(a)enterprisedb.com> wrote: Jaime Casanova wrote: so, is this idea (having some user processes be "tied" to postmaster start/stop) going to somewhere? I've added this to the TODO list. Now we just need someone to write it. i... 22 Feb 2010 14:09

Reason why set-value functions not allowed in GREATEST(), etc?
2010/2/22 Hitoshi Harada <umi.tanuki(a)gmail.com>: I just wonder why generate_series() is not allowed in GREATEST syntax. Looking through execQual.c,  almost all syntactic evaluations like COALESCE, ARRAY[], ROW() doesn't allow set-value functions. Could someone tell the underlying reason? Also, using ... 22 Feb 2010 16:25

Wire protocol docs
Dave Page wrote: On Tue, Oct 13, 2009 at 6:24 PM, Tom Lane <tgl(a)sss.pgh.pa.us> wrote: Dave Page <dpage(a)pgadmin.org> writes: Right. My complaint though, is that the docs imply that the info on how those values get set is in the docs somewhere, which appears to be incorrect. The libpq ... 22 Feb 2010 14:09

transaction_isolation vs.default_transaction_isolation
Josh Berkus wrote: Yeah, they basically have semantics specified by the SQL standard that are not compatible with anything else in GUC land. They are more like SET LOCAL settings, but again not quite. Mind you, transaction_isolation and transaction_read_only aren't documented anywhere in o... 22 Feb 2010 14:09

[HACKERS] Reason why set-value functions not allowed in GREATEST(), etc?
I just wonder why generate_series() is not allowed in GREATEST syntax. Looking through execQual.c, almost all syntactic evaluations like COALESCE, ARRAY[], ROW() doesn't allow set-value functions. Could someone tell the underlying reason? Also, using variadic functions introduced since 8.4, I hope we can remove... 22 Feb 2010 12:59

Plans for 9.1, Grouping Sets, disablingmultiqueries, contrib module for string, plpgpsm, preload dictionaries
Pavel Stehule escribi�: Hello, * Now I am working on migration of plpgpsm to plpgsql 9.0 base. I hope so I understand SQL/PSM well so I am able to write production quality implementation. If you like, I can integrate it to core. It can share about 40-50% code with plpgpsm. The behave of plpgpsm is sa... 22 Feb 2010 10:44