Re: postmaster errors with index on temp table? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: postmaster errors with index on temp table?
Date
Msg-id 25555.963212400@sss.pgh.pa.us
Whole thread Raw
In response to postmaster errors with index on temp table?  (Philip Warner <pjw@rhyme.com.au>)
List pgsql-hackers
Philip Warner <pjw@rhyme.com.au> writes:
> Is this a known problem?

> pjw=# create temporary table tt(f int4);
> CREATE
> pjw=# create index tt_ix1 on tt(f);
> CREATE
> pjw=# \q

> The postmaster says:

> NOTICE:  mdopen: couldn't open pg_temp.31633.1: No such file or directory
> pq_flush: send() failed: Bad file descriptor
> NOTICE:  RelationIdBuildRelation: smgropen(pg_temp.31633.1): Bad file
> descriptor
> pq_flush: send() failed: Bad file descriptor

I see the same.  "DROP INDEX tt_ix1" seems to do the right things, but
maybe temp-file cleanup fails to delink the index from its table.
Or, could temp-file cleanup be trying to delete these in the wrong
order?

The notices look pretty harmless, and AFAICT the tables do get cleaned
up, but it's ugly nonetheless...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Re: [BUGS] Unnexpected results using to_number()
Next
From: Karel Zak
Date:
Subject: Re: Per-database/schema settings