[COMMITTERS] pgsql: Add: > o Allow PL/PgSQL RETURN to return row or record
Log Message: --- Add: > o Allow PL/PgSQL RETURN to return row or record functions > > http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php Modified Files: -- pgsql/doc: TODO (r1.1877 -> r1.1878) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1877&r2=1.1878) pgsql/doc/src/FAQ: TODO.html (r1.380 -> r1.381) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.380&r2=1.381) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Clarify dynamic pl/pgsql item and add URLs.
Log Message: --- Clarify dynamic pl/pgsql item and add URLs. Restructure server-side section into PL/pgSQL and non-PL/pgSQL sections: < o Fix PL/pgSQL RENAME to work on variables other than OLD/NEW < o Allow function parameters to be passed by name, < get_employee_salary(emp_id => 12345, tax_year => 2001) < o Add Oracle-style packages < o Add table function support to pltcl, plpython < o Add capability to create and call PROCEDURES < o Allow PL/pgSQL to handle %TYPE arrays, e.g. tab.col%TYPE[] < o Allow function argument names to be statements from PL/PgSQL < o Add MOVE to PL/pgSQL < o Add support for polymorphic arguments and return types to < languages other than PL/PgSQL < o Add support for OUT and INOUT parameters to languages other < than PL/PgSQL < o Add single-step debugging of PL/PgSQL functions < o Allow PL/PgSQL to support WITH HOLD cursors < o Allow PL/PgSQL RETURN to return row or record functions < < http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php > o PL/pgSQL > o Fix RENAME to work on variables other than OLD/NEW > o Allow function parameters to be passed by name, > get_employee_salary(emp_id => 12345, tax_year => 2001) > o Add Oracle-style packages > o Allow handling of %TYPE arrays, e.g. tab.col%TYPE[] > o Allow listing of record column names, and access to > record columns via variables, e.g. columns := r.(*), > tval2 := r.(colname) > > > http://archives.postgresql.org/pgsql-patches/2005-07/msg00458.php > > http://archives.postgresql.org/pgsql-patches/2006-05/msg00302.php > > http://archives.postgresql.org/pgsql-patches/2006-06/msg00031.php > > o Add MOVE > o Add single-step debugging of functions > o Add support for WITH HOLD cursors > o Allow PL/RETURN to return row or record functions > > > http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php > > > o Other > o Add table function support to pltcl, plpython > o Add support for polymorphic arguments and return types to > languages other than PL/PgSQL > o Add capability to create and call PROCEDURES > o Add support for OUT and INOUT parameters to languages other > than PL/PgSQL Modified Files: -- pgsql/doc: TODO (r1.1878 -> r1.1879) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1878&r2=1.1879) pgsql/doc/src/FAQ: TODO.html (r1.381 -> r1.382) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.381&r2=1.382) ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [COMMITTERS] pgsql: Clarify dynamic pl/pgsql item and add URLs.
[EMAIL PROTECTED] (Bruce Momjian) writes: >> o Allow function parameters to be passed by name, >> get_employee_salary(emp_id => 12345, tax_year => 2001) The odds of that syntax getting accepted may not be exactly zero, but they are certainly vanishingly small. I thought we'd agreed that a usable syntax would be like get_employee_salary(12345 AS emp_id, 2001 AS tax_year) regards, tom lane ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: Add: > > o Fix memory leak from exceptions > >
Log Message: --- Add: > > o Fix memory leak from exceptions > > > http://archives.postgresql.org/pgsql-performance/2006-06/msg00305.php Modified Files: -- pgsql/doc: TODO (r1.1879 -> r1.1880) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1879&r2=1.1880) pgsql/doc/src/FAQ: TODO.html (r1.382 -> r1.383) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.382&r2=1.383) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Move list of supported to_ascii() encodings from footnote to main
Log Message: --- Move list of supported to_ascii() encodings from footnote to main description. Nis Jorgensen Modified Files: -- pgsql/doc/src/sgml: func.sgml (r1.319 -> r1.320) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/func.sgml.diff?r1=1.319&r2=1.320) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Update syntax suggestion: < get_employee_salary(emp_id =>
Log Message: --- Update syntax suggestion: < get_employee_salary(emp_id => 12345, tax_year => 2001) > get_employee_salary(emp_id AS 12345, tax_year AS 2001) Modified Files: -- pgsql/doc: TODO (r1.1880 -> r1.1881) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1880&r2=1.1881) pgsql/doc/src/FAQ: TODO.html (r1.383 -> r1.384) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.383&r2=1.384) ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [COMMITTERS] pgsql: Clarify dynamic pl/pgsql item and add URLs.
Tom Lane wrote: > [EMAIL PROTECTED] (Bruce Momjian) writes: > >> o Allow function parameters to be passed by name, > >> get_employee_salary(emp_id => 12345, tax_year => 2001) > > The odds of that syntax getting accepted may not be exactly zero, but > they are certainly vanishingly small. I thought we'd agreed that a > usable syntax would be like > get_employee_salary(12345 AS emp_id, 2001 AS tax_year) TODO updated, but I thought "=>" was the Oracle syntax. -- Bruce Momjian http://candle.pha.pa.us EnterpriseDBhttp://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Add mention that preload_libraries check the magic block, so
Log Message: --- Add mention that preload_libraries check the magic block, so non-PostgreSQL libraries cannot be loaded using this capability. Modified Files: -- pgsql/doc/src/sgml: config.sgml (r1.61 -> r1.62) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/config.sgml.diff?r1=1.61&r2=1.62) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Fix to_ascii() markup error.
Log Message: --- Fix to_ascii() markup error. Modified Files: -- pgsql/doc/src/sgml: func.sgml (r1.320 -> r1.321) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/func.sgml.diff?r1=1.320&r2=1.321) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [COMMITTERS] pgsql: Clarify dynamic pl/pgsql item and add URLs.
On Thu, Jun 15, 2006 at 01:42:10PM -0400, Bruce Momjian wrote: > Tom Lane wrote: > > [EMAIL PROTECTED] (Bruce Momjian) writes: > > >> o Allow function parameters to be passed by name, > > >> get_employee_salary(emp_id => 12345, tax_year => 2001) > > > > The odds of that syntax getting accepted may not be exactly zero, > > but they are certainly vanishingly small. I thought we'd agreed > > that a usable syntax would be like get_employee_salary(12345 AS > > emp_id, 2001 AS tax_year) > > TODO updated, but I thought "=>" was the Oracle syntax. It is. I understand Tom's concern about not unnecessarily grabbing operator symbols, but in this case, I believe it's overblown. Cheers, D -- David Fetter <[EMAIL PROTECTED]> http://fetter.org/ phone: +1 415 235 3778AIM: dfetter666 Skype: davidfetter Remember to vote! ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [COMMITTERS] pgsql: Clarify dynamic pl/pgsql item and add URLs.
David Fetter wrote: > On Thu, Jun 15, 2006 at 01:42:10PM -0400, Bruce Momjian wrote: > > Tom Lane wrote: > > > [EMAIL PROTECTED] (Bruce Momjian) writes: > > > >> o Allow function parameters to be passed by name, > > > >> get_employee_salary(emp_id => 12345, tax_year => 2001) > > > > > > The odds of that syntax getting accepted may not be exactly zero, > > > but they are certainly vanishingly small. I thought we'd agreed > > > that a usable syntax would be like get_employee_salary(12345 AS > > > emp_id, 2001 AS tax_year) > > > > TODO updated, but I thought "=>" was the Oracle syntax. > > It is. I understand Tom's concern about not unnecessarily grabbing > operator symbols, but in this case, I believe it's overblown. Interesting. Seems it is something we will have to discuss when we get closer to a patch. -- Bruce Momjian http://candle.pha.pa.us EnterpriseDBhttp://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] pgsql: Add STRICT to PL/pgSQL SELECT INTO, so exceptions are thrown if
Log Message: --- Add STRICT to PL/pgSQL SELECT INTO, so exceptions are thrown if more or less than one row is returned by the SELECT, for Oracle PL/SQL compatibility. Improve SELECT INTO documentation. Matt Miller Modified Files: -- pgsql/doc/src/sgml: plpgsql.sgml (r1.95 -> r1.96) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/plpgsql.sgml.diff?r1=1.95&r2=1.96) pgsql/src/pl/plpgsql/src: gram.y (r1.91 -> r1.92) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpgsql/src/gram.y.diff?r1=1.91&r2=1.92) pl_exec.c (r1.170 -> r1.171) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpgsql/src/pl_exec.c.diff?r1=1.170&r2=1.171) plerrcodes.h (r1.7 -> r1.8) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpgsql/src/plerrcodes.h.diff?r1=1.7&r2=1.8) plpgsql.h (r1.75 -> r1.76) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpgsql/src/plpgsql.h.diff?r1=1.75&r2=1.76) scan.l (r1.50 -> r1.51) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpgsql/src/scan.l.diff?r1=1.50&r2=1.51) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Use posix_fadvise() to avoid kernel caching of WAL contents on
Log Message: --- Use posix_fadvise() to avoid kernel caching of WAL contents on WAL file close. ITAGAKI Takahiro Modified Files: -- pgsql/src/backend/access/transam: xlog.c (r1.237 -> r1.238) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c.diff?r1=1.237&r2=1.238) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [COMMITTERS] pgsql: Clarify dynamic pl/pgsql item and add URLs.
Bruce Momjian writes: > Tom Lane wrote: >> The odds of that syntax getting accepted may not be exactly zero, but >> they are certainly vanishingly small. I thought we'd agreed that a >> usable syntax would be like >> get_employee_salary(12345 AS emp_id, 2001 AS tax_year) > TODO updated, but I thought "=>" was the Oracle syntax. So? We don't support Oracle's brain-dead outer join syntax either. regards, tom lane ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [COMMITTERS] pgsql: Clarify dynamic pl/pgsql item and add URLs.
Tom Lane wrote: > Bruce Momjian writes: > > Tom Lane wrote: > >> The odds of that syntax getting accepted may not be exactly zero, but > >> they are certainly vanishingly small. I thought we'd agreed that a > >> usable syntax would be like > >> get_employee_salary(12345 AS emp_id, 2001 AS tax_year) > > > TODO updated, but I thought "=>" was the Oracle syntax. > > So? We don't support Oracle's brain-dead outer join syntax either. We had reasonable problems with Oracle's outer-join syntax, while I don't see the same fundamental issue with => vs AS, and PL/pgSQL is patterned on Oracle's PL/SQL. -- Bruce Momjian http://candle.pha.pa.us EnterpriseDBhttp://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [COMMITTERS] pgsql: Clarify dynamic pl/pgsql item and add URLs.
Bruce Momjian writes: > We had reasonable problems with Oracle's outer-join syntax, while I > don't see the same fundamental issue with => vs AS, and PL/pgSQL is > patterned on Oracle's PL/SQL. The fundamental issue is reserving what used to be an available operator name, in the service of a syntax that's not got anything to recommend it other than being Oracle-compatible. AS is already a fully reserved word, so we'd be taking no risk of breaking anyone's app if we use it. And plpgsql has got nothing to do with this, because we're talking SQL syntax not plpgsql. regards, tom lane ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] fulldisjunction - fd: Changed the generate alternatives algorithm to use
Log Message: --- Changed the generate alternatives algorithm to use components instead of JCC heuristic. Fixed the output bug. Fixed a bug in varUnSetNthBitFromLeft. moved to deformed tuple in generate alternative tuple set. Modified Files: -- fd: algstructs.c (r1.8 -> r1.9) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/fulldisjunction/fd/algstructs.c.diff?r1=1.8&r2=1.9) algstructs.h (r1.6 -> r1.7) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/fulldisjunction/fd/algstructs.h.diff?r1=1.6&r2=1.7) algutils.c (r1.6 -> r1.7) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/fulldisjunction/fd/algutils.c.diff?r1=1.6&r2=1.7) algutils.h (r1.6 -> r1.7) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/fulldisjunction/fd/algutils.h.diff?r1=1.6&r2=1.7) odmbfd.c (r1.9 -> r1.10) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/fulldisjunction/fd/odmbfd.c.diff?r1=1.9&r2=1.10) queues.c (r1.8 -> r1.9) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/fulldisjunction/fd/queues.c.diff?r1=1.8&r2=1.9) queues.h (r1.3 -> r1.4) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/fulldisjunction/fd/queues.h.diff?r1=1.3&r2=1.4) queuesfuncs.h (r1.5 -> r1.6) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/fulldisjunction/fd/queuesfuncs.h.diff?r1=1.5&r2=1.6) tset.c (r1.4 -> r1.5) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/fulldisjunction/fd/tset.c.diff?r1=1.4&r2=1.5) tset.h (r1.4 -> r1.5) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/fulldisjunction/fd/tset.h.diff?r1=1.4&r2=1.5) tsetfuncs.h (r1.3 -> r1.4) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/fulldisjunction/fd/tsetfuncs.h.diff?r1=1.3&r2=1.4) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Update magic block wording for preloaded libraries.
Log Message: --- Update magic block wording for preloaded libraries. Modified Files: -- pgsql/doc/src/sgml: config.sgml (r1.62 -> r1.63) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/config.sgml.diff?r1=1.62&r2=1.63) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] pgsql: Fix: < get_employee_salary(emp_id AS 12345, tax_year AS
Log Message: --- Fix: < get_employee_salary(emp_id AS 12345, tax_year AS 2001) > get_employee_salary(12345 AS emp_id, 2001 AS tax_year) Modified Files: -- pgsql/doc: TODO (r1.1881 -> r1.1882) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1881&r2=1.1882) pgsql/doc/src/FAQ: TODO.html (r1.384 -> r1.385) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.384&r2=1.385) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Test for POSIX_FADV_DONTNEED to use posix_fadvise().
Log Message: --- Test for POSIX_FADV_DONTNEED to use posix_fadvise(). Modified Files: -- pgsql/src/backend/access/transam: xlog.c (r1.238 -> r1.239) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c.diff?r1=1.238&r2=1.239) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] npgsql - Npgsql: 2006-06-16 Francisco Figueiredo Jr.
Log Message: --- 2006-06-16 Francisco Figueiredo Jr. <[EMAIL PROTECTED]> * NpgsqlTypesHelper.cs: [#1000551] Incorrect conversion of decimal type causes ERROR: 22P02: invalid input syntax for type numeric. When using prepared commands, decimal numbers were being sent with wrong culture. Now it is sent correctly with InvariantCulture. Thanks Radomir Simic (strasha at gmail dot com), Valentin Gjorgjioski (gjorgjioski at gmail dot com) and Artem Gelun (admin at enoteka dot ru) for tests and feedback. Modified Files: -- Npgsql/src/NpgsqlTypes: NpgsqlTypesHelper.cs (r1.52 -> r1.53) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql/src/NpgsqlTypes/NpgsqlTypesHelper.cs.diff?r1=1.52&r2=1.53) ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
