Обсуждение: BUG #14003: Error "could not open relation with OID 18152875"

Поиск
Список
Период
Сортировка

BUG #14003: Error "could not open relation with OID 18152875"

От
g.jalmi@tcs.com
Дата:
The following bug has been logged on the website:

Bug reference:      14003
Logged by:          Ganesh Jalmi
Email address:      g.jalmi@tcs.com
PostgreSQL version: 9.1.14
Operating system:   CentOS release 6.5
Description:

DB :  "PostgreSQL 9.1.14 on x86_64-unknown-linux-gnu, compiled by gcc (GCC)
4.4.7 20120313 (Red Hat 4.4.7-4), 64-bit"

Scenario:  A temporary table is created within a function where no schema
name is specefied for the table. This table is created using dynamic sql.
  --------------------
    v_out_data:='temp_table_'||to_char(current_timestamp,'DDMMYYHHMISS');
    v_sel_query := 'create temporary table '||v_out_data||'(segment character
varying,Market_mod_type character varying,min_date date, max_date date,
all_ist character varying, service_type character varying, cur_data
character varying, error_message text, error_code integer)';
    execute(v_sel_query);
-------------------------------
    Next a cursor is opened on with select clause dynamically on one of
internal table.
     Based on cursor conditions records gets inserted into the Temporary
Table.
    close the cursor
        return all records from temporary table  and then drop the temorary
table.
------------------------------------

    return query
    execute('select * from '||v_out_data);
    execute('drop table '||v_out_data);

------------------------------------
    while executing drop table command we geet the error "could not open
relation with OID 18152875"

Re: BUG #14003: Error "could not open relation with OID 18152875"

От
Tom Lane
Дата:
g.jalmi@tcs.com writes:
> PostgreSQL version: 9.1.14

> Scenario:  A temporary table is created within a function where no schema
> name is specefied for the table. This table is created using dynamic sql.
>     close the cursor
>         return all records from temporary table  and then drop the temorary
> table.

It's hard to be sure since you didn't provide a concrete test case, but
this sounds very much like a bug that was fixed last September (in 9.1.19
and its sibling releases); see
http://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=dae1c9480

If updating to 9.1.19 or 9.1.20 doesn't fix it, please provide an
exact script to reproduce the problem.

            regards, tom lane