From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, Bruce Momjian <bruce(at)momjian(dot)us>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: [HACKERS] COPY with no WAL, in certain circumstances |
Date: | 2007-01-07 11:59:02 |
Message-ID: | 20070107115902.GB19187@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Sun, Jan 07, 2007 at 11:46:29AM +0000, Simon Riggs wrote:
> On Sun, 2007-01-07 at 03:53 -0500, Tom Lane wrote:
> > "Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
> > > The patch sets HEAP_XMIN_COMMITTED on all of the rows loaded by COPY as
> > > well.
> >
> > I think you just talked yourself out of getting this patch applied.
>
> Maybe; what would be your explanation? Do you have a failure case you
> know of? Perhaps if one exists, there is another route.
One thing I pondered while looking at this: how do you know the user is
going to commit the transaction after the COPY is complete. Could they
run analyze or vacuum or some other DDL command on the table that would
get confused by the disparity between the hint bits and the xlog.
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-01-07 12:35:20 | Re: proposal: catch warnings |
Previous Message | Simon Riggs | 2007-01-07 11:46:29 | Re: COPY with no WAL, in certain circumstances |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-01-07 13:07:00 | Re: [HACKERS] COPY with no WAL, in certain circumstances |
Previous Message | Simon Riggs | 2007-01-07 11:46:29 | Re: COPY with no WAL, in certain circumstances |