Re: Avoid MVCC using exclusive lock possible?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Paul Tillotson <pntil(at)shentel(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Avoid MVCC using exclusive lock possible?
Date: 2004-03-02 01:30:39
Message-ID: 26727.1078191039@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Paul Tillotson <pntil(at)shentel(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2004-03-02 01:32:43 Re: log_line_info
Previous Message Tom Lane 2004-03-02 01:28:02 Re: [HACKERS] CHECK constraints inconsistencies