Your patch has been added to the PostgreSQL unapplied patches list at:
http://candle.pha.pa.us/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
Dmitry Tkach wrote:
> Ok, this sit around for
Without showing the database being dumped, the entire output of
pg_dumpall seems pretty useless so you may as well pipe the whole output
to /dev/null. I don't think a quiet feature for pg_dumpall has enough
use for ordinary users. Sorry.
-
Bruce Momjian <[EMAIL PROTECTED]> writes:
> With no solution on the horizon, and the author saying it fixes some of
> his trigger queries, I am inclined to apply this. I don't see any
> downside except for some extra pfrees if we ever fix this.
Sure, apply away. I was mainly expressing my angst
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > With no solution on the horizon, and the author saying it fixes some of
> > his trigger queries, I am inclined to apply this. I don't see any
> > downside except for some extra pfrees if we ever fix this.
>
> Sure, apply away. I wa
With no solution on the horizon, and the author saying it fixes some of
his trigger queries, I am inclined to apply this. I don't see any
downside except for some extra pfrees if we ever fix this.
---
Dmitry Tkach wrote:
>
Dan Brown ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
can't store {digits} using JDBC
Long Description
We are using the JDBC driver, and are losing partial data. Whenever we try to store
{digits} (note: exactly as shown w
