I saw some where that if I recompiled my server with
MAKE_EXPIRED_TUPLES_VISIBLE I would be able to see deleted rows?

I did a ./configure --enable-MAKE_EXPIRED_TUPLES_VISIBLE

It compiled ok but I dont see the deleted tuples



---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

Tony Caduto <tony_caduto@amsoftwaredesign.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...2/msg00126.php

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Tom Lane wrote:

>Tony Caduto <tony_caduto@amsoftwaredesign.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...2/msg00126.php
>
> regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 6: explain analyze is your friend
>
>
>
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 accidentliy deleted 2600 rows that I would like to get back, so I gave
MAKE_EXPIRED_TUPLES_VISIBLE a try.


Thanks,

Tony

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

On Thu, 2 Feb 2006, Tony Caduto wrote:

> Tom Lane wrote:
>
> >Tony Caduto <tony_caduto@amsoftwaredesign.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...2/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.



---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Stephan Szabo wrote:

>I think something like
>CFLAGS="-D MAKE_EXPIRED_TUPLES_VISIBLE" ./configure
>would be the way to get it.
>
>
>

Thanks,
I worked like a charm once I knew it was a CFLAG.

I did the dump as plain text insert statements, verified the deleted
records where there, then restored into a temp database, deleted all
records I did not need, then
dumped/restored back into the original table.

Thanks to Bruce for including this in 8.1, if used properly it's a life
saver :-)

Tony

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq