| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Fabrízio Mello <fabriziomello(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal "VACUUM SCHEMA" |
| Date: | 2014-12-24 01:09:27 |
| Message-ID: | 549A1247.2030802@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/23/14, 7:44 AM, Robert Haas wrote:
> On Mon, Dec 22, 2014 at 5:00 PM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
>> I would MUCH rather that we find a way to special-case executing
>> non-transactional commands dynamically, because VACUUM isn't the only one
>> that suffers from this problem.
>
> Is pg_background a solution to this problem?
Yes, since it allows you to do "autonomous transactions". It's probably not the most efficient way to solve this, but it should work.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabrízio de Royes Mello | 2014-12-24 02:49:40 | Re: Proposal "VACUUM SCHEMA" |
| Previous Message | Jim Nasby | 2014-12-24 01:06:25 | Re: Proposal "VACUUM SCHEMA" |