mirror of
https://github.com/postgres/postgres.git
synced 2026-04-15 22:10:45 -04:00
873cb8fca9
ALTER TABLE commands in an extension script are added to an event
trigger command list; but starting with commit b5810de3f4 they do so in
a memory context that's too short-lived, so when execution ends and time
comes to use the entries, they've already been freed.
(This would also be a problem with ALTER TABLE commands in a
multi-command query string, but these serendipitously end in
PortalContext -- which probably explains why it took so long for this to
be reported.)
Fix by using the memory context specifically set for that, instead.
Backpatch to 13, where the aforementioned commit appeared.
Reported-by: Philippe Beaudoin
Author: Jehan-Guillaume de Rorthais <jgdr@dalibo.com>
Discussion: https://postgr.es/m/20200902193715.6e0269d4@firost
7 lines
358 B
SQL
7 lines
358 B
SQL
/* src/test/modules/test_extensions/test_event_trigger--1.0--2.0.sql */
|
|
-- complain if script is sourced in psql, rather than via ALTER EXTENSION
|
|
\echo Use "ALTER EXTENSION test_event_trigger UPDATE TO '2.0'" to load this file. \quit
|
|
|
|
-- Test extension upgrade with event trigger.
|
|
ALTER EVENT TRIGGER table_rewrite_trg DISABLE;
|
|
ALTER TABLE t DROP COLUMN id;
|