GUC vs variable.c (was Patches applied...) - Mailing list pgsql-hackers

From Tom Lane
Subject GUC vs variable.c (was Patches applied...)
Date
Msg-id 27276.1019425938@sss.pgh.pa.us
Whole thread Raw
List pgsql-hackers
thomas@postgresql.org (Thomas Lockhart) writes:
> Log message:
>     Remove the definition for set_name_needs_quotes() on the assumption that
>     it is now obsolete. Need some regression test cases to prove otherwise...

I agree that we don't want to reinstate that hack on the gram.y side.
However, it seems to me way past time that we did what needs to be done
with variable.c --- ie, get rid of it.  All these special-cased
variables should be folded into GUC.

The code as committed has some problems beyond having broken support
for search_path with a list:

regression=# set seed to 1,2;
server closed the connection unexpectedly

(crash is due to assert failure)

but really there's no point in worrying about that one case.  What we
need to do is figure out what needs to be done to GUC to let it support
these variables, and then merge the variable.c code into that structure.

Should we allow GUC stuff to take a list of A_Const as being the most
general case, or is that overkill?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Joe Conway
Date:
Subject: Re: Patches applied; initdb time!
Next
From: Thomas Lockhart
Date:
Subject: Re: Patches applied; initdb time!