Seems it is known bug. I am documenting it with this patch. We can't
seem to think of a clean way to fix it properly.
---
Frank van Vugt wrote:
> L.S.
>
> It seems that '\encoding' only shows the correct client encoding i
Just put in the queue.
---
Nathan Mueller wrote:
> Has anyone looked at these yet?
>
> --Nate
>
> ---(end of broadcast)---
> TIP 5: Have you checked our extensive FAQ
D. Wright ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
PostgreSQL 7.3 and 7.3.1 fails to compile pg_dump
Long Description
While I can get PostgreSQL 7.2 to compile fine on my machine (running FreeBSD), I can
not get 7.3 or 7
[EMAIL PROTECTED] writes:
> Then, when I run gmake, I get the following error:
> pg_dump.c:192: elements of array `long_options' have incomplete type
> pg_dump.c:193: warning: excess elements in struct initializer after `long_options[0]'
> pg_dump.c:193: `no_argument' undeclared (first use in this
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
Nathan Mueller wrote:
> I was playing aro
I have CC'ed D'Arcy asking for info.
---
Tom Lane wrote:
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > Tom, Bruce: who has the python interface these days?
>
> D'Arcy still is the lead guy on it, I think. Looking at the CVS
