| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alan Li <ali(at)truviso(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Greg Smith <gsmith(at)gregsmith(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: 8.4 open item: copy performance regression? |
| Date: | 2009-06-22 16:42:47 |
| Message-ID: | 4A3FB487.30409@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>
>> Tom Lane wrote:
>>
>>> I thought he was asking for a solution to the problem of WALInsertLock
>>> contention. In any case, we have "WAL bypass on a table by table basis"
>>> now, don't we?
>>>
>
>
>> If we do I'm ignorant of it ;-) How do we say "Never WAL this table"?
>>
>
> Make it a temporary table.
>
>
>
That doesn't help if you need the data visible in multiple sessions. But
we're digressing from the original topic. Sorry.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Wanner | 2009-06-22 16:55:57 | Re: Synch Rep: communication between backends and walsender |
| Previous Message | Tom Lane | 2009-06-22 16:37:24 | Re: BUG #4862: different results in to_date() between 8.3.7 & 8.4.RC1 |