Thank you very much, Tom. That was it. Our other server is running 9.1.9
and that's why it worked there.
On Tue, Aug 27, 2013 at 10:50 PM, Tom Lane wrote:
> Moshe Jacobson writes:
> > On Tue, Aug 20, 2013 at 7:58 PM, Tom Lane wrote:
> >> Well, I think you did it wrong, or else you're using a
Moshe Jacobson writes:
> On Tue, Aug 20, 2013 at 7:58 PM, Tom Lane wrote:
>> Well, I think you did it wrong, or else you're using a PG version that
>> predates some necessary fix, because it works for me.
> Sorry for the delayed response. I am using postgres 9.1.4 with pg_dump of
> the same vers
On Tue, Aug 20, 2013 at 7:58 PM, Tom Lane wrote:
>
> Well, I think you did it wrong, or else you're using a PG version that
> predates some necessary fix, because it works for me.
>
> To debug, you might try looking in pg_extension to see if the extconfig
> entry for your extension includes the
Moshe Jacobson writes:
> I can pg_dump our prod database and pg_restore it onto our dev server with
> zero errors, but once I try to pg_dump the dev copy again, that's when I
> receive the errors above.
> I didn't drop & recreate the extension to fix it on prod -- I just created
> a new version of
On Tue, Aug 20, 2013 at 4:03 PM, Tom Lane wrote:
> It's pretty hard to believe that that would work in pg_dump but not
> pg_dumpall. You sure the error references a database that you fixed the
> sequence definition in? (You'd probably have to drop and recreate the
> extension to fix it in an ex
Moshe Jacobson writes:
> In searching for a solution I found an old message where Tom suggested
> marking the sequence as a config table in the same way. This seems to work
> OK when I use pg_dump, but for some reason, pg_dumpall generates the
> following error:
It's pretty hard to believe that t
I wrote an extension and marked one of the tables it creates as a config
table using pg_extension_config_dump(). This caused the data to be dumped
and restored correctly, but the sequence attached to the PK column was not
correctly set to its old value.
In searching for a solution I found an old m
