On 1/28/15 10:25 PM, Tom Lane wrote:
Stephen Frost sfr...@snowman.net writes:
* David Johnston (david.g.johns...@gmail.com) wrote:
Fair enough but reset to what? I don't know the internal mechanics but
if the session default is warning and a local change sets it to notice
then an
* David Johnston (david.g.johns...@gmail.com) wrote:
On Wednesday, January 28, 2015, Stephen Frost sfr...@snowman.net wrote:
Ehh.. Shouldn't we try to take a bit more care that we reset things
after a CREATE EXTENSION is run? Not really sure how much effort we
want to put into it, but I
On Wednesday, January 28, 2015, Stephen Frost sfr...@snowman.net wrote:
* David G Johnston (david.g.johns...@gmail.com javascript:;) wrote:
Jerry Sievers-3 wrote
Hackers; I noticed this trying to import a large pg_dump file with
warnings supressed.
It seems loading pgq sets
Stephen Frost sfr...@snowman.net writes:
* David Johnston (david.g.johns...@gmail.com) wrote:
Fair enough but reset to what? I don't know the internal mechanics but
if the session default is warning and a local change sets it to notice
then an unconditional reset would not get us back to the
Hackers; I noticed this trying to import a large pg_dump file with
warnings supressed.
It seems loading pgq sets client_min_messages to warning and leaves it
this way which defeats an attempt to change the setting prior and have
it stick.
I tested with several other extensions in same DB and
Jerry Sievers-3 wrote
Hackers; I noticed this trying to import a large pg_dump file with
warnings supressed.
It seems loading pgq sets client_min_messages to warning and leaves it
this way which defeats an attempt to change the setting prior and have
it stick.
I tested with several other
* David G Johnston (david.g.johns...@gmail.com) wrote:
Jerry Sievers-3 wrote
Hackers; I noticed this trying to import a large pg_dump file with
warnings supressed.
It seems loading pgq sets client_min_messages to warning and leaves it
this way which defeats an attempt to change the
