Re: Restore LargeObjects on different server

From: Durumdara <durumdara(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Restore LargeObjects on different server
Date: 2017-10-12 10:41:49
Message-ID: CAEcMXhnDQYjzPbqgJgPVKPybBhuB2PBbJgcsJZ7-kez2Ab2k4w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi!

Somebody wrote me that:

The pg_catalog schema is system schema, but it is IN the DB.

Is this true? So OID is not global (out from DB)?

So we can dump and restore the DB with OIDs without collision in new server?

Thank you!

dd

2017-10-12 11:35 GMT+02:00 Durumdara <durumdara(at)gmail(dot)com>:

> Dear Members!
>
> Because of upload/download progress we used LargeObjects to store some
> files in one of our database (and not bytea).
>
> Only this database uses the OID-s of these files.
>
> In the near future we must move to another server.
> This new server is also working now, the moving of databases is continous,
> one by one.
>
> The main problem that LargeObjects are stored in the system table(s). Same
> OIDs could links to different LargeObjects.
>
> The old and new PGSQL server may have same OID values (160606 f. e.) with
> different content (LargeObject).
> In old this is one of our file data, in the new this is a table's system
> definition.
>
> Can we backup this database WITH OIDs, and restore it in new server
> without worrying of LargeObject overwriting?
>
> Or how to migrate (move) this database with largeobjects in new to
> preserve the consistency of copied database and lobs, but preserve the
> existing OID/largeobject pairs in new server?
>
> Thank you for the info/help!
>
> Best regards
> dd
>
>
>
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Laurenz Albe 2017-10-12 12:15:54 Re: Restore LargeObjects on different server
Previous Message KES 2017-10-12 10:01:06 Re: BUG #14850: Implement optinal additinal parameter for 'justify' date/time function