Re: BUG #7756: When upgrading postgis extension get row is too big: size 9272, maximum size 8160 - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #7756: When upgrading postgis extension get row is too big: size 9272, maximum size 8160
Date
Msg-id 7346.1355778796@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #7756: When upgrading postgis extension get row is too big: size 9272, maximum size 8160  ("Paragon Corporation" <lr@pcorp.us>)
Responses Re: BUG #7756: When upgrading postgis extension get row is too big: size 9272, maximum size 8160
List pgsql-bugs
"Paragon Corporation" <lr@pcorp.us> writes:
> Attached is a fake_postgis extension that you can just copy the files to
> your extension folder that can produce the error if you run the below:

Great, thanks for the test case.

> I assumed that the :
> pg_catalog.pg_extension_config_dump
> Calls would overwrite each subsequent for a given object for a given
> extension.  So I have that in my upgrade script as well should we add more
> spatial_ref_sys records we want to avoid dumping.
> It seems it just adds.

It probably should overwrite --- this is something we simply didn't
consider in the original coding.

The other case I was considering is that ALTER EXTENSION DROP should
probably remove any extconfig entry for a table that you disassociate
from the extension.

            regards, tom lane

pgsql-bugs by date:

Previous
From: "Paragon Corporation"
Date:
Subject: Re: BUG #7756: When upgrading postgis extension get row is too big: size 9272, maximum size 8160
Next
From: cstanley@cstanley.no-ip.biz
Date:
Subject: BUG #7757: Trouble with PostgreSQL loading a large csv file into a table