rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
postgresql/src/test/regress/expected/guc.out

561 lines
9.6 KiB
Plaintext
Raw Normal View History

Extend 'guc' regression test to check manipulations of datestyle as well as vacuum_cost_delay. Since datestyle is a string variable, this exercises memory allocation issues that might not appear when modifying an integer GUC variable. Also, we can observe the side effects of changing datestyle to check that assign hooks are called at the right times.
2006-08-13 21:31:06 +02:00
-- pg_regress should ensure that this default value applies; however
-- we can't rely on any specific default value of vacuum_cost_delay
SHOW datestyle;
DateStyle
---------------
Postgres, MDY
(1 row)
-- SET to some nondefault value
Add some basic tests of GUC behavior. Joachim Wieland
2006-08-04 02:00:14 +02:00
SET vacuum_cost_delay TO 400;
Extend 'guc' regression test to check manipulations of datestyle as well as vacuum_cost_delay. Since datestyle is a string variable, this exercises memory allocation issues that might not appear when modifying an integer GUC variable. Also, we can observe the side effects of changing datestyle to check that assign hooks are called at the right times.
2006-08-13 21:31:06 +02:00
SET datestyle = 'ISO, YMD';
Add some basic tests of GUC behavior. Joachim Wieland
2006-08-04 02:00:14 +02:00
SHOW vacuum_cost_delay;
vacuum_cost_delay
-------------------
400ms
(1 row)
Extend 'guc' regression test to check manipulations of datestyle as well as vacuum_cost_delay. Since datestyle is a string variable, this exercises memory allocation issues that might not appear when modifying an integer GUC variable. Also, we can observe the side effects of changing datestyle to check that assign hooks are called at the right times.
2006-08-13 21:31:06 +02:00
SHOW datestyle;
DateStyle
-----------
ISO, YMD
(1 row)
SELECT '2006-08-13 12:34:56'::timestamptz;
timestamptz
------------------------
2006-08-13 12:34:56-07
(1 row)
Add some basic tests of GUC behavior. Joachim Wieland
2006-08-04 02:00:14 +02:00
-- SET LOCAL has no effect outside of a transaction
SET LOCAL vacuum_cost_delay TO 500;
SHOW vacuum_cost_delay;
vacuum_cost_delay
-------------------
400ms
(1 row)
Extend 'guc' regression test to check manipulations of datestyle as well as vacuum_cost_delay. Since datestyle is a string variable, this exercises memory allocation issues that might not appear when modifying an integer GUC variable. Also, we can observe the side effects of changing datestyle to check that assign hooks are called at the right times.
2006-08-13 21:31:06 +02:00
SET LOCAL datestyle = 'SQL';
SHOW datestyle;
DateStyle
-----------
ISO, YMD
(1 row)
SELECT '2006-08-13 12:34:56'::timestamptz;
timestamptz
------------------------
2006-08-13 12:34:56-07
(1 row)
Add some basic tests of GUC behavior. Joachim Wieland
2006-08-04 02:00:14 +02:00
-- SET LOCAL within a transaction that commits
BEGIN;
SET LOCAL vacuum_cost_delay TO 500;
SHOW vacuum_cost_delay;
vacuum_cost_delay
-------------------
500ms
(1 row)
Extend 'guc' regression test to check manipulations of datestyle as well as vacuum_cost_delay. Since datestyle is a string variable, this exercises memory allocation issues that might not appear when modifying an integer GUC variable. Also, we can observe the side effects of changing datestyle to check that assign hooks are called at the right times.
2006-08-13 21:31:06 +02:00
SET LOCAL datestyle = 'SQL';
SHOW datestyle;
DateStyle
-----------
SQL, YMD
(1 row)
SELECT '2006-08-13 12:34:56'::timestamptz;
timestamptz
-------------------------
08/13/2006 12:34:56 PDT
(1 row)
Add some basic tests of GUC behavior. Joachim Wieland
2006-08-04 02:00:14 +02:00
COMMIT;
SHOW vacuum_cost_delay;
vacuum_cost_delay
-------------------
400ms
(1 row)
Extend 'guc' regression test to check manipulations of datestyle as well as vacuum_cost_delay. Since datestyle is a string variable, this exercises memory allocation issues that might not appear when modifying an integer GUC variable. Also, we can observe the side effects of changing datestyle to check that assign hooks are called at the right times.
2006-08-13 21:31:06 +02:00
SHOW datestyle;
DateStyle
-----------
ISO, YMD
(1 row)
SELECT '2006-08-13 12:34:56'::timestamptz;
timestamptz
------------------------
2006-08-13 12:34:56-07
(1 row)
Add some basic tests of GUC behavior. Joachim Wieland
2006-08-04 02:00:14 +02:00
-- SET should be reverted after ROLLBACK
BEGIN;
SET vacuum_cost_delay TO 600;
SHOW vacuum_cost_delay;
vacuum_cost_delay
-------------------
600ms
(1 row)
Extend 'guc' regression test to check manipulations of datestyle as well as vacuum_cost_delay. Since datestyle is a string variable, this exercises memory allocation issues that might not appear when modifying an integer GUC variable. Also, we can observe the side effects of changing datestyle to check that assign hooks are called at the right times.
2006-08-13 21:31:06 +02:00
SET datestyle = 'German';
SHOW datestyle;
DateStyle
-------------
German, DMY
(1 row)
SELECT '2006-08-13 12:34:56'::timestamptz;
timestamptz
-------------------------
13.08.2006 12:34:56 PDT
(1 row)
Add some basic tests of GUC behavior. Joachim Wieland
2006-08-04 02:00:14 +02:00
ROLLBACK;
SHOW vacuum_cost_delay;
vacuum_cost_delay
-------------------
400ms
(1 row)
Extend 'guc' regression test to check manipulations of datestyle as well as vacuum_cost_delay. Since datestyle is a string variable, this exercises memory allocation issues that might not appear when modifying an integer GUC variable. Also, we can observe the side effects of changing datestyle to check that assign hooks are called at the right times.
2006-08-13 21:31:06 +02:00
SHOW datestyle;
DateStyle
-----------
ISO, YMD
(1 row)
SELECT '2006-08-13 12:34:56'::timestamptz;
timestamptz
------------------------
2006-08-13 12:34:56-07
(1 row)
Add some basic tests of GUC behavior. Joachim Wieland
2006-08-04 02:00:14 +02:00
-- Some tests with subtransactions
BEGIN;
SET vacuum_cost_delay TO 700;
Extend 'guc' regression test to check manipulations of datestyle as well as vacuum_cost_delay. Since datestyle is a string variable, this exercises memory allocation issues that might not appear when modifying an integer GUC variable. Also, we can observe the side effects of changing datestyle to check that assign hooks are called at the right times.
2006-08-13 21:31:06 +02:00
SET datestyle = 'MDY';
SHOW datestyle;
DateStyle
-----------
ISO, MDY
(1 row)
SELECT '2006-08-13 12:34:56'::timestamptz;
timestamptz
------------------------
2006-08-13 12:34:56-07
(1 row)
Add some basic tests of GUC behavior. Joachim Wieland
2006-08-04 02:00:14 +02:00
SAVEPOINT first_sp;
SET vacuum_cost_delay TO 800;
SHOW vacuum_cost_delay;
vacuum_cost_delay
-------------------
Extend 'guc' regression test to check manipulations of datestyle as well as vacuum_cost_delay. Since datestyle is a string variable, this exercises memory allocation issues that might not appear when modifying an integer GUC variable. Also, we can observe the side effects of changing datestyle to check that assign hooks are called at the right times.
2006-08-13 21:31:06 +02:00
800ms
(1 row)
SET datestyle = 'German, DMY';
SHOW datestyle;
DateStyle
-------------
German, DMY
(1 row)
SELECT '2006-08-13 12:34:56'::timestamptz;
timestamptz
-------------------------
13.08.2006 12:34:56 PDT
(1 row)
ROLLBACK TO first_sp;
SHOW datestyle;
DateStyle
-----------
ISO, MDY
(1 row)
SELECT '2006-08-13 12:34:56'::timestamptz;
timestamptz
------------------------
2006-08-13 12:34:56-07
Add some basic tests of GUC behavior. Joachim Wieland
2006-08-04 02:00:14 +02:00
(1 row)
SAVEPOINT second_sp;
SET vacuum_cost_delay TO 900;
Extend 'guc' regression test to check manipulations of datestyle as well as vacuum_cost_delay. Since datestyle is a string variable, this exercises memory allocation issues that might not appear when modifying an integer GUC variable. Also, we can observe the side effects of changing datestyle to check that assign hooks are called at the right times.
2006-08-13 21:31:06 +02:00
SET datestyle = 'SQL, YMD';
SHOW datestyle;
DateStyle
-----------
SQL, YMD
(1 row)
SELECT '2006-08-13 12:34:56'::timestamptz;
timestamptz
-------------------------
08/13/2006 12:34:56 PDT
(1 row)
Add some basic tests of GUC behavior. Joachim Wieland
2006-08-04 02:00:14 +02:00
SAVEPOINT third_sp;
SET vacuum_cost_delay TO 1000;
SHOW vacuum_cost_delay;
vacuum_cost_delay
-------------------
1s
(1 row)
Extend 'guc' regression test to check manipulations of datestyle as well as vacuum_cost_delay. Since datestyle is a string variable, this exercises memory allocation issues that might not appear when modifying an integer GUC variable. Also, we can observe the side effects of changing datestyle to check that assign hooks are called at the right times.
2006-08-13 21:31:06 +02:00
SET datestyle = 'Postgres, MDY';
SHOW datestyle;
DateStyle
---------------
Postgres, MDY
(1 row)
SELECT '2006-08-13 12:34:56'::timestamptz;
timestamptz
------------------------------
Sun Aug 13 12:34:56 2006 PDT
(1 row)
Add some basic tests of GUC behavior. Joachim Wieland
2006-08-04 02:00:14 +02:00
ROLLBACK TO third_sp;
SHOW vacuum_cost_delay;
vacuum_cost_delay
-------------------
900ms
(1 row)
Extend 'guc' regression test to check manipulations of datestyle as well as vacuum_cost_delay. Since datestyle is a string variable, this exercises memory allocation issues that might not appear when modifying an integer GUC variable. Also, we can observe the side effects of changing datestyle to check that assign hooks are called at the right times.
2006-08-13 21:31:06 +02:00
SHOW datestyle;
DateStyle
-----------
SQL, YMD
(1 row)
SELECT '2006-08-13 12:34:56'::timestamptz;
timestamptz
-------------------------
08/13/2006 12:34:56 PDT
(1 row)
Add some basic tests of GUC behavior. Joachim Wieland
2006-08-04 02:00:14 +02:00
ROLLBACK TO second_sp;
SHOW vacuum_cost_delay;
vacuum_cost_delay
-------------------
700ms
(1 row)
Extend 'guc' regression test to check manipulations of datestyle as well as vacuum_cost_delay. Since datestyle is a string variable, this exercises memory allocation issues that might not appear when modifying an integer GUC variable. Also, we can observe the side effects of changing datestyle to check that assign hooks are called at the right times.
2006-08-13 21:31:06 +02:00
SHOW datestyle;
DateStyle
-----------
ISO, MDY
(1 row)
SELECT '2006-08-13 12:34:56'::timestamptz;
timestamptz
------------------------
2006-08-13 12:34:56-07
(1 row)
Add some basic tests of GUC behavior. Joachim Wieland
2006-08-04 02:00:14 +02:00
ROLLBACK;
Extend 'guc' regression test to check manipulations of datestyle as well as vacuum_cost_delay. Since datestyle is a string variable, this exercises memory allocation issues that might not appear when modifying an integer GUC variable. Also, we can observe the side effects of changing datestyle to check that assign hooks are called at the right times.
2006-08-13 21:31:06 +02:00
SHOW vacuum_cost_delay;
vacuum_cost_delay
-------------------
400ms
(1 row)
SHOW datestyle;
DateStyle
-----------
ISO, YMD
(1 row)
SELECT '2006-08-13 12:34:56'::timestamptz;
timestamptz
------------------------
2006-08-13 12:34:56-07
(1 row)
Add some basic tests of GUC behavior. Joachim Wieland
2006-08-04 02:00:14 +02:00
-- SET LOCAL with Savepoints
BEGIN;
SHOW vacuum_cost_delay;
vacuum_cost_delay
-------------------
400ms
(1 row)
Extend 'guc' regression test to check manipulations of datestyle as well as vacuum_cost_delay. Since datestyle is a string variable, this exercises memory allocation issues that might not appear when modifying an integer GUC variable. Also, we can observe the side effects of changing datestyle to check that assign hooks are called at the right times.
2006-08-13 21:31:06 +02:00
SHOW datestyle;
DateStyle
-----------
ISO, YMD
(1 row)
SELECT '2006-08-13 12:34:56'::timestamptz;
timestamptz
------------------------
2006-08-13 12:34:56-07
(1 row)
Add some basic tests of GUC behavior. Joachim Wieland
2006-08-04 02:00:14 +02:00
SAVEPOINT sp;
SET LOCAL vacuum_cost_delay TO 300;
SHOW vacuum_cost_delay;
vacuum_cost_delay
-------------------
300ms
(1 row)
Extend 'guc' regression test to check manipulations of datestyle as well as vacuum_cost_delay. Since datestyle is a string variable, this exercises memory allocation issues that might not appear when modifying an integer GUC variable. Also, we can observe the side effects of changing datestyle to check that assign hooks are called at the right times.
2006-08-13 21:31:06 +02:00
SET LOCAL datestyle = 'Postgres, MDY';
SHOW datestyle;
DateStyle
---------------
Postgres, MDY
(1 row)
SELECT '2006-08-13 12:34:56'::timestamptz;
timestamptz
------------------------------
Sun Aug 13 12:34:56 2006 PDT
(1 row)
Add some basic tests of GUC behavior. Joachim Wieland
2006-08-04 02:00:14 +02:00
ROLLBACK TO sp;
SHOW vacuum_cost_delay;
vacuum_cost_delay
-------------------
400ms
(1 row)
Extend 'guc' regression test to check manipulations of datestyle as well as vacuum_cost_delay. Since datestyle is a string variable, this exercises memory allocation issues that might not appear when modifying an integer GUC variable. Also, we can observe the side effects of changing datestyle to check that assign hooks are called at the right times.
2006-08-13 21:31:06 +02:00
SHOW datestyle;
DateStyle
-----------
ISO, YMD
(1 row)
SELECT '2006-08-13 12:34:56'::timestamptz;
timestamptz
------------------------
2006-08-13 12:34:56-07
(1 row)
Add some basic tests of GUC behavior. Joachim Wieland
2006-08-04 02:00:14 +02:00
ROLLBACK;
Extend 'guc' regression test to check manipulations of datestyle as well as vacuum_cost_delay. Since datestyle is a string variable, this exercises memory allocation issues that might not appear when modifying an integer GUC variable. Also, we can observe the side effects of changing datestyle to check that assign hooks are called at the right times.
2006-08-13 21:31:06 +02:00
SHOW vacuum_cost_delay;
vacuum_cost_delay
-------------------
400ms
(1 row)
SHOW datestyle;
DateStyle
-----------
ISO, YMD
(1 row)
SELECT '2006-08-13 12:34:56'::timestamptz;
timestamptz
------------------------
2006-08-13 12:34:56-07
(1 row)
Add some basic tests of GUC behavior. Joachim Wieland
2006-08-04 02:00:14 +02:00
-- SET followed by SET LOCAL
BEGIN;
SET vacuum_cost_delay TO 400;
SET LOCAL vacuum_cost_delay TO 500;
SHOW vacuum_cost_delay;
vacuum_cost_delay
-------------------
500ms
(1 row)
Extend 'guc' regression test to check manipulations of datestyle as well as vacuum_cost_delay. Since datestyle is a string variable, this exercises memory allocation issues that might not appear when modifying an integer GUC variable. Also, we can observe the side effects of changing datestyle to check that assign hooks are called at the right times.
2006-08-13 21:31:06 +02:00
SET datestyle = 'ISO, DMY';
SET LOCAL datestyle = 'Postgres, MDY';
SHOW datestyle;
DateStyle
---------------
Postgres, MDY
(1 row)
SELECT '2006-08-13 12:34:56'::timestamptz;
timestamptz
------------------------------
Sun Aug 13 12:34:56 2006 PDT
(1 row)
Add some basic tests of GUC behavior. Joachim Wieland
2006-08-04 02:00:14 +02:00
COMMIT;
SHOW vacuum_cost_delay;
vacuum_cost_delay
-------------------
400ms
(1 row)
Extend 'guc' regression test to check manipulations of datestyle as well as vacuum_cost_delay. Since datestyle is a string variable, this exercises memory allocation issues that might not appear when modifying an integer GUC variable. Also, we can observe the side effects of changing datestyle to check that assign hooks are called at the right times.
2006-08-13 21:31:06 +02:00
SHOW datestyle;
DateStyle
-----------
ISO, DMY
(1 row)
SELECT '2006-08-13 12:34:56'::timestamptz;
timestamptz
------------------------
2006-08-13 12:34:56-07
(1 row)
Add some basic tests of GUC behavior. Joachim Wieland
2006-08-04 02:00:14 +02:00
--
-- Test RESET. We use datestyle because the reset value is forced by
-- pg_regress, so it doesn't depend on the installation's configuration.
--
SET datestyle = iso, ymd;
SHOW datestyle;
DateStyle
-----------
ISO, YMD
(1 row)
Extend 'guc' regression test to check manipulations of datestyle as well as vacuum_cost_delay. Since datestyle is a string variable, this exercises memory allocation issues that might not appear when modifying an integer GUC variable. Also, we can observe the side effects of changing datestyle to check that assign hooks are called at the right times.
2006-08-13 21:31:06 +02:00
SELECT '2006-08-13 12:34:56'::timestamptz;
timestamptz
------------------------
2006-08-13 12:34:56-07
(1 row)
Add some basic tests of GUC behavior. Joachim Wieland
2006-08-04 02:00:14 +02:00
RESET datestyle;
SHOW datestyle;
DateStyle
---------------
Postgres, MDY
(1 row)
Extend 'guc' regression test to check manipulations of datestyle as well as vacuum_cost_delay. Since datestyle is a string variable, this exercises memory allocation issues that might not appear when modifying an integer GUC variable. Also, we can observe the side effects of changing datestyle to check that assign hooks are called at the right times.
2006-08-13 21:31:06 +02:00
SELECT '2006-08-13 12:34:56'::timestamptz;
timestamptz
------------------------------
Sun Aug 13 12:34:56 2006 PDT
(1 row)
RESET SESSION, plus related new DDL commands. Patch from Marko Kreen, reviewed by Neil Conway. This patch adds the following DDL command variants: RESET SESSION, RESET TEMP, RESET PLANS, CLOSE ALL, and DEALLOCATE ALL. RESET SESSION is intended for use by connection pool software and the like, in order to reset a client session to something close to its initial state. Note that while most of these command variants can be executed inside a transaction block (but are not transaction-aware!), RESET SESSION cannot. While this is inconsistent, it is intended to catch programmer mistakes: RESET SESSION in an open transaction block is probably unintended.
2007-04-12 08:53:49 +02:00
--
Rename the newly-added commands for discarding session state. RESET SESSION, RESET PLANS, and RESET TEMP are now DISCARD ALL, DISCARD PLANS, and DISCARD TEMP, respectively. This is to avoid confusion with the pre-existing RESET variants: the DISCARD commands are not actually similar to RESET. Patch from Marko Kreen, with some minor editorialization.
2007-04-26 18:13:15 +02:00
-- Test DISCARD TEMP
RESET SESSION, plus related new DDL commands. Patch from Marko Kreen, reviewed by Neil Conway. This patch adds the following DDL command variants: RESET SESSION, RESET TEMP, RESET PLANS, CLOSE ALL, and DEALLOCATE ALL. RESET SESSION is intended for use by connection pool software and the like, in order to reset a client session to something close to its initial state. Note that while most of these command variants can be executed inside a transaction block (but are not transaction-aware!), RESET SESSION cannot. While this is inconsistent, it is intended to catch programmer mistakes: RESET SESSION in an open transaction block is probably unintended.
2007-04-12 08:53:49 +02:00
--
CREATE TEMP TABLE reset_test ( data text ) ON COMMIT DELETE ROWS;
SELECT relname FROM pg_class WHERE relname = 'reset_test';
relname
------------
reset_test
(1 row)
Rename the newly-added commands for discarding session state. RESET SESSION, RESET PLANS, and RESET TEMP are now DISCARD ALL, DISCARD PLANS, and DISCARD TEMP, respectively. This is to avoid confusion with the pre-existing RESET variants: the DISCARD commands are not actually similar to RESET. Patch from Marko Kreen, with some minor editorialization.
2007-04-26 18:13:15 +02:00
DISCARD TEMP;
RESET SESSION, plus related new DDL commands. Patch from Marko Kreen, reviewed by Neil Conway. This patch adds the following DDL command variants: RESET SESSION, RESET TEMP, RESET PLANS, CLOSE ALL, and DEALLOCATE ALL. RESET SESSION is intended for use by connection pool software and the like, in order to reset a client session to something close to its initial state. Note that while most of these command variants can be executed inside a transaction block (but are not transaction-aware!), RESET SESSION cannot. While this is inconsistent, it is intended to catch programmer mistakes: RESET SESSION in an open transaction block is probably unintended.
2007-04-12 08:53:49 +02:00
SELECT relname FROM pg_class WHERE relname = 'reset_test';
relname
---------
(0 rows)
--
Rename the newly-added commands for discarding session state. RESET SESSION, RESET PLANS, and RESET TEMP are now DISCARD ALL, DISCARD PLANS, and DISCARD TEMP, respectively. This is to avoid confusion with the pre-existing RESET variants: the DISCARD commands are not actually similar to RESET. Patch from Marko Kreen, with some minor editorialization.
2007-04-26 18:13:15 +02:00
-- Test DISCARD ALL
RESET SESSION, plus related new DDL commands. Patch from Marko Kreen, reviewed by Neil Conway. This patch adds the following DDL command variants: RESET SESSION, RESET TEMP, RESET PLANS, CLOSE ALL, and DEALLOCATE ALL. RESET SESSION is intended for use by connection pool software and the like, in order to reset a client session to something close to its initial state. Note that while most of these command variants can be executed inside a transaction block (but are not transaction-aware!), RESET SESSION cannot. While this is inconsistent, it is intended to catch programmer mistakes: RESET SESSION in an open transaction block is probably unintended.
2007-04-12 08:53:49 +02:00
--
-- do changes
DECLARE foo CURSOR WITH HOLD FOR SELECT 1;
PREPARE foo AS SELECT 1;
LISTEN foo_event;
SET vacuum_cost_delay = 13;
CREATE TEMP TABLE tmp_foo (data text) ON COMMIT DELETE ROWS;
CREATE ROLE temp_reset_user;
SET SESSION AUTHORIZATION temp_reset_user;
-- look changes
SELECT relname FROM pg_listener;
relname
-----------
foo_event
(1 row)
SELECT name FROM pg_prepared_statements;
name
------
foo
(1 row)
SELECT name FROM pg_cursors;
name
------
foo
(1 row)
SHOW vacuum_cost_delay;
vacuum_cost_delay
-------------------
13ms
(1 row)
SELECT relname from pg_class where relname = 'tmp_foo';
relname
---------
tmp_foo
(1 row)
SELECT current_user = 'temp_reset_user';
?column?
----------
t
(1 row)
Rename the newly-added commands for discarding session state. RESET SESSION, RESET PLANS, and RESET TEMP are now DISCARD ALL, DISCARD PLANS, and DISCARD TEMP, respectively. This is to avoid confusion with the pre-existing RESET variants: the DISCARD commands are not actually similar to RESET. Patch from Marko Kreen, with some minor editorialization.
2007-04-26 18:13:15 +02:00
-- discard everything
DISCARD ALL;
RESET SESSION, plus related new DDL commands. Patch from Marko Kreen, reviewed by Neil Conway. This patch adds the following DDL command variants: RESET SESSION, RESET TEMP, RESET PLANS, CLOSE ALL, and DEALLOCATE ALL. RESET SESSION is intended for use by connection pool software and the like, in order to reset a client session to something close to its initial state. Note that while most of these command variants can be executed inside a transaction block (but are not transaction-aware!), RESET SESSION cannot. While this is inconsistent, it is intended to catch programmer mistakes: RESET SESSION in an open transaction block is probably unintended.
2007-04-12 08:53:49 +02:00
-- look again
SELECT relname FROM pg_listener;
relname
---------
(0 rows)
SELECT name FROM pg_prepared_statements;
name
------
(0 rows)
SELECT name FROM pg_cursors;
name
------
(0 rows)
SHOW vacuum_cost_delay;
vacuum_cost_delay
-------------------
0
(1 row)
SELECT relname from pg_class where relname = 'tmp_foo';
relname
---------
(0 rows)
SELECT current_user = 'temp_reset_user';
?column?
----------
f
(1 row)
DROP ROLE temp_reset_user;
Implement function-local GUC parameter settings, as per recent discussion. There are still some loose ends: I didn't do anything about the SET FROM CURRENT idea yet, and it's not real clear whether we are happy with the interaction of SET LOCAL with function-local settings. The documentation is a bit spartan, too.
2007-09-03 02:39:26 +02:00
--
-- Tests for function-local GUC settings
--
set regex_flavor = advanced;
create function report_guc(text) returns text as
$$ select current_setting($1) $$ language sql
set regex_flavor = basic;
select report_guc('regex_flavor'), current_setting('regex_flavor');
report_guc | current_setting
------------+-----------------
basic | advanced
(1 row)
-- this should draw only a warning
alter function report_guc(text) set search_path = no_such_schema;
NOTICE: schema "no_such_schema" does not exist
-- with error occurring here
select report_guc('regex_flavor'), current_setting('regex_flavor');
ERROR: schema "no_such_schema" does not exist
alter function report_guc(text) reset search_path set regex_flavor = extended;
select report_guc('regex_flavor'), current_setting('regex_flavor');
report_guc | current_setting
------------+-----------------
extended | advanced
(1 row)
alter function report_guc(text) reset all;
select report_guc('regex_flavor'), current_setting('regex_flavor');
report_guc | current_setting
------------+-----------------
advanced | advanced
(1 row)