From: | Szymon Guz <mabewlun(at)gmail(dot)com> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: issues with dropped columns in plpgsql code again |
Date: | 2013-05-07 20:41:11 |
Message-ID: | CAFjNrYuCAEj9WioOz-10Bx4+gfdsO0YMVAPU_bKsybwipNQUsg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 7 May 2013 21:23, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> sorry
>
> my test
>
> create table f1(a int, b int, c varchar, dropped_column numeric, d
> varchar);
>
> create or replace function f1_trg()
> returns trigger as $$
> declare _f1_var f1;
> begin raise notice 'run trigger';
> _f1_var := new;
> return _f1_var;
> end;
> $$ language plpgsql;
>
> create trigger xx before insert on f1 for row execute procedure f1_trg();
>
> insert into f1 values(1,1,'aaa',1.1,'aaa');
> alter table f1 drop column dropped_column ;
>
> insert into f1 values(1,1,'aaa','aaa');
>
>
>
Fails for me as well. I managed to run the last query either with
restarting session, or disabling the trigger.
Checked that on PostgreSQL 9.2.4 on x86_64-unknown-linux-gnu, compiled by
gcc (Ubuntu/Linaro 4.7.2-2ubuntu1) 4.7.2, 64-bit
regards,
Szymon
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2013-05-07 21:28:11 | local_preload_libraries logspam |
Previous Message | Jeff Janes | 2013-05-07 19:48:29 | Re: XLogFlush invoked about twice as much after 9.2 group commit enhancement |