Re: Renaming sequence auto generated by SERIAL type don't update pg_attrdef - Mailing list pgsql-jdbc

From Oliver Jowett
Subject Re: Renaming sequence auto generated by SERIAL type don't update pg_attrdef
Date
Msg-id 49B5E208.1080205@opencloud.com
Whole thread Raw
In response to Re: Renaming sequence auto generated by SERIAL type don't update pg_attrdef  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Renaming sequence auto generated by SERIAL type don't update pg_attrdef  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-jdbc
Tom Lane wrote:
> "Dickson S. Guedes" <listas@guedesoft.net> writes:
>> Shouldn't the JDBC driver use another query instead that, since docs
>> alerts[1] to this problem?
>
> What's the default value being used for anyway?  If it's to determine
> which sequence is associated with the column, I think you shouldn't be
> looking at pg_attrdef at all; you should look for a dependent sequence
> via pg_depend.  But maybe it's only being used to check if the column
> has a default, in which case the possible staleness of the string
> value isn't important.

I'm guessing that particular query is from
DatabaseMetaData.getColumns(), which returns amongst other things:

13. COLUMN_DEF String => default value (may be null)

(yes, that's the sum total of the JDBC documentation about that piece of
metadata)

-O

pgsql-jdbc by date:

Previous
From: Scott Carey
Date:
Subject: Re: [PERFORM] Query much slower when run from postgres function
Next
From: Tom Lane
Date:
Subject: Re: Renaming sequence auto generated by SERIAL type don't update pg_attrdef