| From: | Tim <elatllat(at)gmail(dot)com> |
|---|---|
| To: | Josh Kupershmidt <schmiddy(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, David Fetter <david(at)fetter(dot)org>, Aron Wieck <me(at)eunice(dot)de> |
| Subject: | Re: vacuumlo patch |
| Date: | 2011-08-07 07:54:28 |
| Message-ID: | CA+3zgmvoXAGQUJgqHC6D21-JckaWZHf+jJaS6Jz48P=X4TBD4Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Josh's message On Sun, Aug 7, 2011 at 2:36 AM:
> could we figure out what that limit should be based on
> max_locks_per_transaction?
It would be nice to implement via "-l max" instead of making users do it
manually or something like this "-l $(grep "max_locks_per_transaction.*="
postgresql.conf | perl -p -e 's/#.*//g;s/^.*?([0-9]+).*?$/$1/g' | grep .
|head -1 )".
For this patch I just want to enable the limit functionality, leaving higher
level options like max to the user for now.
> handle deleting all the ophan LOs in several transactions for the user
> automatically?
>
I addressed this option before and basically said it is an undesirable
alternative because It is a less flexible option that is easily implemented
in a shell script.
Again it would be a welcome extra option but it can be left to the user for
now.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2011-08-07 07:57:23 | Will switchover still need a checkpoint in 9.1 SR Hot Standby |
| Previous Message | Peter Eisentraut | 2011-08-07 07:49:21 | Re: vacuumlo patch |