Re: [BUGS] BUG #1956: Plpgsql top-level DECLARE does not share

2005-10-15 Thread Karl O. Pinc
On 10/14/2005 09:30:51 AM, Michael Fuhr wrote: On Thu, Oct 13, 2005 at 03:51:15PM +, Karl O. Pinc wrote: > I definately do not recall catching any additional errors at > compile time as part of the switch to 8. 8.0's syntax checking is minimal; 8.1's will be better.

Re: [BUGS] BUG #1956: Plpgsql top-level DECLARE does not share

2005-10-14 Thread Karl O. Pinc
On 10/13/2005 09:38:36 AM, Bruce Momjian wrote: > Fair enough. At the same time it sure would be nice if > plpgsql actually compiled (and parsed SQL) at > function definition time, even when the result is thrown away. > I'm building a big system and it's quite annoying > to get syntax errors,

Re: [BUGS] BUG #1956: Plpgsql top-level DECLARE does not share

2005-10-14 Thread Karl O. Pinc
On 10/13/2005 03:24:23 PM, Tom Lane wrote: "Jim C. Nasby" <[EMAIL PROTECTED]> writes: > On Thu, Oct 13, 2005 at 01:30:56PM -0400, Tom Lane wrote: >> Basically, DECLARE introduces a new name scope that wouldn't be there >> if you didn't say DECLARE. Without some bizarre reinterpretation of the >

Re: [BUGS] BUG #1956: Plpgsql top-level DECLARE does not share

2005-10-13 Thread Karl O. Pinc
On 10/12/2005 10:32:20 PM, Bruce Momjian wrote: We tend to follow the C conventions, so perhaps we should throw a warning, but I can't think of any cases where we throw a warning in plpgsql because we compile it once on first call. I am thinking this falls in the "don't do that" category. F

[BUGS] BUG #1956: Plpgsql top-level DECLARE does not share scope with CREATE FUNCTION

2005-10-12 Thread Karl O. Pinc
The following bug has been logged online: Bug reference: 1956 Logged by: Karl O. Pinc Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.3 Operating system: Linux Description:Plpgsql top-level DECLARE does not share scope with CREATE FUNCTION Details

[BUGS] On line manual pages need easy access to TOC

2005-04-02 Thread Karl O. Pinc
Hi, It's a real pain to have to go to the bottom of the on-line manual pages to get back to the table of contents (I seem to want to do this all the time.) A link at the top would be nice. You could either add a "Home" link like at the bottom, or simply make the manual version number hot. Regards

[BUGS] BUG #1565: SRPM does not rebuild due to krb5.h

2005-03-26 Thread Karl O. Pinc
The following bug has been logged online: Bug reference: 1565 Logged by: Karl O. Pinc Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.1 Operating system: Linux CentOS 3.3 Description:SRPM does not rebuild due to krb5.h Details: I'm using CentOS 3.3

Re: [BUGS] pg_dumpall (7.3) 'public' schema bug

2004-11-16 Thread Karl O. Pinc
On 2004.11.16 16:25 Tom Lane wrote: "Karl O. Pinc" <[EMAIL PROTECTED]> writes: > I deleted the 'public' schema from my databases > in 7.3, now in 7.4 they are back. IMHO this is not a bug. It is not pg_dump's charter to remove system-created objects...

[BUGS] pg_dumpall (7.3) two search_path schema bugs

2004-11-16 Thread Karl O. Pinc
Hi, Went to upgrade from postgresql (RedHat's postgresql rh-postgresql-7.3.6-7) to Fedora core 3 postgresql 7.4.6-1 and encountered a problem. If nothing else this is worth a note on the 7.4 upgrade doc page. It appears as though pg_dumpall is setting the search_path runtime variable in the databa

[BUGS] pg_dumpall (7.3) 'public' schema bug

2004-11-16 Thread Karl O. Pinc
Hi, Went to upgrade from postgresql (RedHat's postgresql rh-postgresql-7.3.6-7) to Fedora core 3 postgresql 7.4.6-1 and encountered a problem. If nothing else this is worth a note on the 7.4 upgrade doc page. I deleted the 'public' schema from my databases in 7.3, now in 7.4 they are back. I supp