| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: log chunking broken with large queries under load |
| Date: | 2012-04-03 21:09:56 |
| Message-ID: | 4F7B6724.2080602@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 04/02/2012 01:03 PM, Tom Lane wrote:
> Andrew Dunstan<andrew(at)dunslane(dot)net> writes:
>> On 04/02/2012 12:44 PM, Tom Lane wrote:
>>> You could do something like having a list of pending chunks for each
>>> value of (pid mod 256). The length of each such list ought to be plenty
>>> short under ordinary circumstances.
>> Yeah, ok, that should work. How big would we make each list to start
>> with? Still 20, or smaller?
> When I said "list", I meant a "List *". No fixed size.
>
>
Ok, like this? Do we consider this a bug fix, to be backpatched?
cheers
andrew
| Attachment | Content-Type | Size |
|---|---|---|
| pgsyslogger2.patch | text/x-patch | 6.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-04-03 21:32:25 | Re: Speed dblink using alternate libpq tuple storage |
| Previous Message | Jay Levitt | 2012-04-03 19:14:44 | Re: Switching to Homebrew as recommended Mac install? |