From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Howie <caffeine(at)toodarkpark(dot)org> |
Cc: | PostgreSQL-general <pgsql-general(at)postgreSQL(dot)org> |
Subject: | Re: [GENERAL] bug in 6.4.2? |
Date: | 1999-05-31 16:10:06 |
Message-ID: | 199905311610.MAA21464@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
>
> i was recently importing a fairly large amount of data from a mysql to
> postgres ( 6.4.2 ). to make a long story short, this involved some
> renames ( alter table foo rename to bar ). two psql clients were running,
> accessing the same database and, in some cases, querying on the same
> table. when one tried to insert into one of the recently
> dropped-and-renamed tables, it produced an error saying that an attribute
> didnt exist for <old table's OID>. a restart of that app fixed it.
>
> fyi, the error was "get_attisset: no attribute requests in relation
> 902432" while doing an insert. a select statement just returned 0 rows,
> even though there were 1 or 2 matching the query ( verified in the psql
> window i was working in, doing the renames ).
>
> is this a known problem ? do the clients cache OIDs or some such ? is
> there anything i can do, apart from the obvious ( heh ), to make sure
> this doesnt happen again ?
In 6.4.*, table renaming was not properly flushing the cache, I think.
Should work fine when 6.5 is released.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1999-05-31 18:11:18 | Re: [GENERAL] bug in 6.4.2? |
Previous Message | Gregory Maxwell | 1999-05-31 15:36:19 | Re: [GENERAL] Upgrading from 6.3->6.4.2/6.5b1 possible |