| From: | Kevin Barnard <kevin(dot)barnard(at)gmail(dot)com> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Table UPDATE is too slow |
| Date: | 2004-09-06 01:19:35 |
| Message-ID: | b068057c040905181998476d1@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-performance |
Do all of the commands to swap tables in a transaction. The table
gets locked briefly but should have a lot less impact then the update
command.
On Mon, 06 Sep 2004 01:28:04 +0200, Marinos J. Yannikos <mjy(at)geizhals(dot)at> wrote:
>
> That said, I'm not entirely sure how well postgres' client libraries can
> deal with tables being renamed while in use, perhaps someone can shed
> some light on this.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Randy Yates | 2004-09-06 02:47:56 | One Database per Data File? |
| Previous Message | Joel | 2004-09-06 01:16:52 | So, would it make sense to do something like a CRC on each record? (was How to determine a database is intact?) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-09-06 02:18:05 | Re: Tanking a server with shared memory |
| Previous Message | Martin Foster | 2004-09-06 01:15:24 | Tanking a server with shared memory |