| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Tim <elatllat(at)gmail(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: vacuumlo patch |
| Date: | 2011-07-25 02:09:07 |
| Message-ID: | 1311559631-sup-8680@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Tim's message of dom jul 24 14:48:08 -0400 2011:
> Please consider adding this minor patch, or offering improvements.
>
> *Problem*: vacuumlo required PostgreSQL to use more locks per transaction
> than possible resulting in an error and a log file full of "ignored until
> end of transaction" warnings.
> (max_locks_per_transaction is limited by shmmax which is limited by RAM)
Interesting. I cannot vouch for or against the patch, but please
resubmit without the -U0 switch.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2011-07-25 02:12:36 | Re: Policy on pulling in code from other projects? |
| Previous Message | Andrew Dunstan | 2011-07-25 00:55:51 | Re: libpq SSL with non-blocking sockets |