Re: Proposal "VACUUM SCHEMA"

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Jim Nasby <Jim(dot)Nasby(at)bluetreble(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-23 13:44:17
Message-ID: CA+Tgmoa8r+CK_uKHVjC9ZGwdowZwAd19oX0b+SctqM-U9NywNQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-12-23 13:46:40 Re: INSERT ... ON CONFLICT {UPDATE | IGNORE}
Previous Message Alvaro Herrera 2014-12-23 13:28:26 Re: Role Attribute Bitmask Catalog Representation