Re: run GUC check hooks on RESET

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Robert Haas" <robertmhaas(at)gmail(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: run GUC check hooks on RESET
Date: 2012-02-16 21:53:59
Message-ID: 4F3D2697020000250004577E@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> The main thing I would be worried about is whether you're sure
> that you have separated the RESET-as-a-command case from the cases
> where we actually are rolling back to a previous state.

It looks good to me. I added a few regression tests for that.


Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> +1 for such a comment.

Added.


The attached patch includes these. If it seems close, I'd be happy
to come up with a version for the 9.1 branch. Basically it looks
like that means omitting the changes to variable.c (which only
changed message text and made the order of steps on related GUCs
more consistent), and capturing a different out file for the
expected directory.

-Kevin

Attachment Content-Type Size
check-reset-v2.patch text/plain 12.3 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-02-16 22:19:54 Re: Command Triggers
Previous Message Guillaume Lelarge 2012-02-16 21:43:48 Bug in intarray?