Re: BUG #11638: Transaction safety fails when constraints are dropped and analyze is done

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: cg(at)osss(dot)net, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #11638: Transaction safety fails when constraints are dropped and analyze is done
Date: 2014-10-15 08:31:54
Message-ID: CAB7nPqR5mpKM6HWh1jE9crWa-8mjri_J9exD3AyYuEEnW0cTQg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Oct 15, 2014 at 3:18 PM, Andres Freund <andres(at)2ndquadrant(dot)com>
wrote:

> On 2014-10-15 15:02:43 +0900, Michael Paquier wrote:
> > Btw, I have just put my hands on this code and made the attached to
> > make vac_update_relstats able to do a transactional update. It looks
> > to work fine with only a check on the flags of vacuum statement.
>
> Have you tested that the problem's now fixed?
>
Yep. In the test case given by Casey the foreign key on the second table is
visible after the rollback.

> Imo this is complex enough to deserve a regression test. Can you add
> one?
>
Definitely makes sense. Here is an updated version.
Regards,
--
Michael

Attachment Content-Type Size
20141015_analyze_transactional.patch text/x-diff 6.3 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Eric Hill 2014-10-15 12:36:55 Re: [BUGS] BUG #11608: ODBC driver crashes after wrong password entered
Previous Message David G Johnston 2014-10-15 06:57:24 Re: BUG #11671: UNACCENT call with constant arg evaluated for each row