geog_brin_inclusion upgrade issue

lr at pcorp.us lr at pcorp.us
Wed Mar 19 13:40:52 PDT 2025


Ah okay sorry misunderstood.  As you were.

> -----Original Message-----
> From: Justin Pryzby <pryzby at telsasoft.com>
> Sent: Wednesday, March 19, 2025 4:35 PM
> To: lr at pcorp.us
> Cc: Paul Ramsey <pramsey at cleverelephant.ca>; postgis-devel at lists.osgeo.org
> Subject: Re: geog_brin_inclusion upgrade issue
> 
> Automatically fixing the issue is what I was talking about, and what I've now
> done.
> 
> On Wed, Mar 19, 2025 at 04:32:20PM -0400, lr at pcorp.us wrote:
> > I don’t think a regular dump / restore would help nailing down the issue,
> because the default dump, just stores CREATE EXTENSION command and
> restore just runs the CREATE EXTENSION from scratch which would
> automatically fix the issue.
> >
> > We’d need the kind of dump that pg_upgrade creates.  I never looked to see
> what command it does to backup the extension contents of the db.
> >
> > From: Paul Ramsey <pramsey at cleverelephant.ca>
> > Sent: Wednesday, March 19, 2025 3:19 PM
> > To: Justin Pryzby <pryzby at telsasoft.com>
> > Cc: Regina Obe <lr at pcorp.us>; PostGIS Development Discussion
> > <postgis-devel at lists.osgeo.org>
> > Subject: Re: geog_brin_inclusion upgrade issue
> >
> > Yeah, if the data are small enough to be tractable for a dump/restore, that’s
> clearly the way to go.
> >
> > On Mar 19, 2025, at 12:10 PM, Justin Pryzby <pryzby at telsasoft.com
> <mailto:pryzby at telsasoft.com> > wrote:
> >
> > There was definitely an upgrade issue, but it's been a few years, and
> > if nobody else has complaind, then it seems like the thing to do might
> > be to drop postgis and reinstall it.



More information about the postgis-devel mailing list