From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
---|---|
To: | Tony Caduto <tony_caduto(at)amsoftwaredesign(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: question about MAKE_EXPIRED_TUPLES_VISIBLE |
Date: | 2006-02-02 22:25:40 |
Message-ID: | 20060202141759.T33004@megazone.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, 2 Feb 2006, Tony Caduto wrote:
> Tom Lane wrote:
>
> >Tony Caduto <tony_caduto(at)amsoftwaredesign(dot)com> writes:
> >
> >
> >>I saw some where that if I recompiled my server with
> >>MAKE_EXPIRED_TUPLES_VISIBLE I would be able to see deleted rows?
> >>
> >>
> >
> >If you aren't a certified wizard you do NOT want to turn that on,
> >because it will very probably help you make things worse. My opinion
> >on it is on record:
> >http://archives.postgresql.org/pgsql-patches/2005-02/msg00126.php
> >
> Well, it does not seem to do anything, I enabled it with ./configure
> --enable-MAKE_EXPIRED_TUPLES_VISIBLE
> I then thought well maybe I need to do dump of the table and the deleted
> tuples would be in there, but no.
>
> ./configure --enable-MAKE_EXPIRED_TUPLES_VISIBLE is the correct way to
> enable it right?
I think something like
CFLAGS="-D MAKE_EXPIRED_TUPLES_VISIBLE" ./configure
would be the way to get it.
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2006-02-02 22:25:43 | Re: Primary keys for companies and people |
Previous Message | Leif B. Kristensen | 2006-02-02 22:11:53 | Re: Primary keys for companies and people |