Re: Restore LargeObjects on different server

From: "Daniel Verite" <daniel(at)manitou-mail(dot)org>
To: "Durumdara" <durumdara(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Restore LargeObjects on different server
Date: 2017-10-13 13:36:10
Message-ID: 977cb03c-3a4d-4af2-86bc-decfe322de68@manitou-mail.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Durumdara wrote:

> The pg_catalog schema is system schema, but it is IN the DB.
>
> Is this true? So OID is not global (out from DB)?

The OID generator is global to the instance, but the unicity
checks are local to the tables that use OIDs, including
large objects.

The case when you may have a problem is if moving
large objects from the old instance/old database
to the new instance/new database but the new
database would already have large objects created
before the import. Then you would need to do a merge
rather than just an import.

But if you're merely in the case that other databases in the new
instance have consumed OIDs and some happen to be equal to the ones
you want to import in a new database, that doesn't matter: similar OIDs
won't conflict if they're in different databases or even the same
database but different tables.

Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Seamus Abshere 2017-10-13 15:49:21 "Shared strings"-style table
Previous Message Alvaro Herrera 2017-10-13 13:04:38 Re: REASSIGN OWNED simply doesn't work