From: | Bill Moran <wmoran(at)potentialtech(dot)com> |
---|---|
To: | Rikard Pavelic <rikard(dot)pavelic(at)zg(dot)htnet(dot)hr> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: problems selecting from altered table |
Date: | 2007-06-19 15:09:39 |
Message-ID: | 20070619110939.173da32c.wmoran@potentialtech.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
In response to Rikard Pavelic <rikard(dot)pavelic(at)zg(dot)htnet(dot)hr>:
>
> I noticed that some of the functions I created don't work anymore.
> So I tired to reproduce the problem and this is what I came up with.
>
> create table test(
> id serial primary key,
> tekst text);
>
> insert into test values(1,'1'),(2,'2');
>
> create function sel_test() returns test as
> $$
> declare red record;
> begin
> select * into red from test limit 1;
> return red;
> end
> $$ language plpgsql;
>
> select * from sel_test();
>
> This all works ok, but if I do
>
> alter table test drop column tekst;
>
> then select * from sel_test(); doesn't work anymore
> Even if I recreate the function.
>
> Is this a known problem?
Have you tried altering the table, then disconnect and reconnect, then run
your stored procedure?
If that works, then the problem has to do with OID caching, which is known.
--
Bill Moran
http://www.potentialtech.com
From | Date | Subject | |
---|---|---|---|
Next Message | Gerhard Hintermayer | 2007-06-19 15:20:25 | Re: Apparent Wraparound? |
Previous Message | Francisco Reyes | 2007-06-19 15:03:24 | Re: pg_restore out of memory |