Re: postmaster errors with index on temp table?

Поиск
Список
Период
Сортировка
Искать
От
Tom Lane
Тема
Re: postmaster errors with index on temp table?
Дата
Msg-id
25555.963212400@sss.pgh.pa.us
Ответ на
Список
Дерево обсуждения
postmaster errors with index on temp table? Philip Warner <pjw@rhyme.com.au>
Re: postmaster errors with index on temp table? Bruce Momjian <pgman@candle.pha.pa.us>
Re: postmaster errors with index on temp table? Philip Warner <pjw@rhyme.com.au>
Re: postmaster errors with index on temp table? Bruce Momjian <pgman@candle.pha.pa.us>
Re: postmaster errors with index on temp table? Philip Warner <pjw@rhyme.com.au>
Re: postmaster errors with index on temp table? Bruce Momjian <pgman@candle.pha.pa.us>
Re: postmaster errors with index on temp table? Tom Lane <tgl@sss.pgh.pa.us>
Re: postmaster errors with index on temp table? Bruce Momjian <pgman@candle.pha.pa.us>
Re: postmaster errors with index on temp table? Tom Lane <tgl@sss.pgh.pa.us>
Philip Warner  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 по дате отправления
От: Tom Lane
Дата:
От: Karel Zak
Дата:
FAQ