| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Paragon Corporation" <lr(at)pcorp(dot)us> |
| Cc: | "'Andres Freund'" <andres(at)2ndquadrant(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #7756: When upgrading postgis extension get row is too big: size 9272, maximum size 8160 |
| Date: | 2012-12-17 21:13:16 |
| Message-ID: | 7346.1355778796@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Paragon Corporation" <lr(at)pcorp(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | cstanley | 2012-12-17 21:32:22 | BUG #7757: Trouble with PostgreSQL loading a large csv file into a table |
| Previous Message | Paragon Corporation | 2012-12-17 21:08:40 | Re: BUG #7756: When upgrading postgis extension get row is too big: size 9272, maximum size 8160 |