Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > FWIW this has been fixed in 8.3, you can drop the item from the 8.4
> > queue. Thanks.
>
> There are a couple of other things on that page that seem already
> applied, for instance hashing for numeric and an early form of the
> seq
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> FWIW this has been fixed in 8.3, you can drop the item from the 8.4
> queue. Thanks.
There are a couple of other things on that page that seem already
applied, for instance hashing for numeric and an early form of the
seq scan ringbuffer patch.
While
Removed.
---
Alvaro Herrera wrote:
> Bruce Momjian escribi?:
> >
> > This has been saved for the 8.4 release:
> >
> > http://momjian.postgresql.org/cgi-bin/pgpatches_hold
>
> FWIW this has been fixed in 8.3, you can d
Bruce Momjian escribió:
>
> This has been saved for the 8.4 release:
>
> http://momjian.postgresql.org/cgi-bin/pgpatches_hold
FWIW this has been fixed in 8.3, you can drop the item from the 8.4
queue. Thanks.
> ---
This has been saved for the 8.4 release:
http://momjian.postgresql.org/cgi-bin/pgpatches_hold
---
Dawid Kuroczko wrote:
> Hello, I have a system where there are mostly COPYs,
> which insert data into a table. Ocasi
Hello, I have a system where there are mostly COPYs,
which insert data into a table. Ocasionally a COPY will fail (and thus,
dead rows appear), but as far as I can tell ROLLBACK is not reflected
anywhere in the pg_stats_user_tables. And since there are no rows
n_tup_upd or n_tup_del, therefore a
