Re: postmaster errors with index on temp table?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: postmaster errors with index on temp table?
Date: 2000-07-10 07:00:00
Message-ID: 25555.963212400@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Philip Warner <pjw(at)rhyme(dot)com(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Karel Zak 2000-07-10 07:11:33 Re: Per-database/schema settings
Previous Message Tom Lane 2000-07-10 06:53:15 Re: [HACKERS] Re: Unnexpected results using to_number()