Re: pg.dropped

From: Greg Smith <greg(at)2ndquadrant(dot)com>
To: Filip Rembiałkowski <plk(dot)zuber(at)gmail(dot)com>
Cc: PG-General Mailing List <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg.dropped
Date: 2010-01-07 21:31:14
Message-ID: 4B4652A2.6020305@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Filip Rembiałkowski wrote:
> After dropping a column from table, there is still entry in pg_attribute
>
> filip(at)la_dev=# select * from pg_attribute where attrelid = (select oid
> from pg_class where relname='thetable') order by attnum desc limit 1;
> -[ RECORD 1 ]-+------------------------------
> attrelid | 4753849
> attname | ........pg.dropped.69........
> ...
> attisdropped | t

See that last part? That's what happens when you drop a
table--"attisdropped" is set to true. The server can't just delete the
pg_attribute entry altogether for various internal reasons, this is what
it does instead.

> And of course this makes my INSERT not working...

There's obviously something wrong here, but the fact that the
pg_attribute entry is still there (but marked dropped) is a not a direct
cause of your problem.

--
Greg Smith 2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
greg(at)2ndQuadrant(dot)com www.2ndQuadrant.com

In response to

  • pg.dropped at 2010-01-07 16:22:49 from Filip Rembiałkowski

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Russell Smith 2010-01-07 23:34:56 Re: A maybe-bug?
Previous Message Chris Ernst 2010-01-07 21:30:31 Re: PG Index

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Page 2010-01-07 21:31:53 Re: RFC: PostgreSQL Add-On Network
Previous Message David E. Wheeler 2010-01-07 21:30:52 Re: RFC: PostgreSQL Add-On Network