FW: [PATCHES] Implementation of SQLSTATE and SQLERRM variables

I have Postgres 8.0.1 on Solaris 9 Sparc machine running in "usr/local/pgsql" directory and my source is in "postgresql-8.0.1/src/pl/plpgsql/src" directory. In "sqlstate.diff" file it is looking " diff -c -r pgsql.old/src/pl/plpgsql/src/gram.y pgsql/src/pl/plpgsql/src/gram.y" checking diff betwe

Re: [PATCHES] Implementation of SQLSTATE and SQLERRM variables

Hi, I have Postgres 8.0.1 on Solaris 9 Sparc machine running in "usr/local/pgsql" directory. I am trying to apply "sqlstate.diff" patch for SQLERRM and SQLSTATE for plpgsql. 1. I have copied "sqlstate.diff" in "postgresql-8.0.1.old/src/pl/plpgsql/src" directory. 2. Executing command: pa

[PATCHES] WIP XLog Switch

WIP patch to perform a switch from one log file to next when we do a pg_stop_backup(), including wal replay handling at recovery time. Patch currently crashes server at various points, so don't stare too hard, but patch applies cleanly on cvstip, compiles and make checks. Main issue is the need

Re: [PATCHES] pg_autovacuum UPDATE_INTERVAL cmd arg

Thomas F.O'Connell wrote: > Well, then it'll probably be moot for 8.1 if all goes well and autovac > gets integrated. > Right, and I am pledged to work to get it into 8.1. -- Bruce Momjian| http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1

Re: [PATCHES] pg_autovacuum UPDATE_INTERVAL cmd arg

Well, then it'll probably be moot for 8.1 if all goes well and autovac gets integrated. -tfo -- Thomas F. O'Connell Co-Founder, Information Architect Sitening, LLC Strategic Open Source: Open Your i™ http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN 37203-6320 615-260-0005 On

Re: [PATCHES] [HACKERS] Implementation of SQLCODE and SQLERRM variables

Pavel Stehule wrote: > Hello, > > I am not sure, I corrected memory problems, I think, but there are some > changes in plpgsql code. I'l update patch today. OK, great thanks. -- Bruce Momjian| http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 35

Re: [PATCHES] [HACKERS] Implementation of SQLCODE and SQLERRM variables

Removed. New version coming. --- Pavel Stehule wrote: > Hello, > > I changed code by your and Neil's notes. The name SQLCODE isn't well, > better is SQLSTATE. It's very similar DB2 variable. I am not sure, so my > solutio

Re: [PATCHES] [HACKERS] Implementation of SQLCODE and SQLERRM variables

Pavel Stehule wrote: > On Tue, 19 Apr 2005, Tom Lane wrote: > > > Bruce Momjian writes: > > > Guys, is this patch ready for application? I think so, but am not 100% > > > sure. > > > > I haven't read the code yet, but in any case I still object to choosing > > Oracle-like names for Oracle-incom

Re: [PATCHES] [HACKERS] Implementation of SQLCODE and SQLERRM variables

Tom Lane wrote: > Bruce Momjian writes: > > Guys, is this patch ready for application? I think so, but am not 100% > > sure. > > I haven't read the code yet, but in any case I still object to choosing > Oracle-like names for Oracle-incompatible functionality. We need to > settle on better names

Re: [PATCHES] [HACKERS] Implementation of SQLCODE and SQLERRM variables

Dinesh Pandey wrote: > Hello All, > > Where can I find patch for SQLERRM/SQLSTATE variable implementation?. > > I am using Postgres 8.0.1. > > Its very urgent because I have an assignment of Porting Oracle's PL?SQL > into PL/pgSQL. Well, right now it is in: http://momjian.postgresq

[PATCHES] Implementation of SQLSTATE and SQLERRM variables

Hello, I updated patch to last changes plpgsql code. Patch contains changes for gram.y, pl_exec.c, plpgsql.h, regress/sql/plpgsql.sql and regress/output/plpgsql.out. I can't to write documenation, my english is terrible. This patch is implementation of variables SQLERRM and SQLSTATE for plpgsq