Non superusers can set log_statement to true but can't set it
back to false even if log_statement was false at the begining of a
connection.
I think lambda users should be able to revert log_statement to
false when false is the default setting.
--
%!PS
297.6 420.9 translate 90 r
I spoted a trouble with the HEAD taged PG version CVS updated
on the 4th of september.
During a COPY FROM stdin query involving a VARCHAR[] column I
experienced troubles with values containing an escaped double quote.
The query was expressed like this on the application side:
"CO
When updating a NULL cell which is an array of something,
setting an adressed member of a non existent array, the value of the
cell is not changed.
> CREATE TABLE dummy (foo INT, bar VARCHAR[]);
CREATE TABLE
> INSERT INTO dummy (foo) VALUES (1);
INSERT 43266442 1
> SELECT bar IS NULL AS i
On Wed, Sep 24, 2003 at 12:09:52AM -0400, Tom Lane wrote:
>
> Assigning to a member of a NULL array has always yielded another NULL
> array. While I've never been particularly satisfied with that behavior
> either, it has some logical symmetry to it. What do you think the
> behavior ought to be?
