Re: Avoid MVCC using exclusive lock possible? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Avoid MVCC using exclusive lock possible?
Date
Msg-id 26727.1078191039@sss.pgh.pa.us
Whole thread Raw
In response to Re: Avoid MVCC using exclusive lock possible?  (Paul Tillotson <pntil@shentel.net>)
List pgsql-hackers
Paul Tillotson <pntil@shentel.net> writes:
> I use this type of approach when mirroring data from a foxpro database 
> (yuck) to a read-only postgres database.  It is quicker and cleaner than 
> deleting all of the rows and inserting them again (TRUNCATE is not 
> transaction safe, which I need).

Just FYI, TRUNCATE *is* transaction safe as of 7.4.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: CHECK constraints inconsistencies
Next
From: Bruno Wolff III
Date:
Subject: Re: CHECK constraints inconsistencies