pgsql: Do not select new object OIDs that match recently-dead entries.

2018-04-11 Thread Tom Lane
Do not select new object OIDs that match recently-dead entries. When selecting a new OID, we take care to avoid picking one that's already in use in the target table, so as not to create duplicates after the OID counter has wrapped around. However, up to now we used SnapshotDirty when scanning

pgsql: Do not select new object OIDs that match recently-dead entries.

2018-04-11 Thread Tom Lane
Do not select new object OIDs that match recently-dead entries. When selecting a new OID, we take care to avoid picking one that's already in use in the target table, so as not to create duplicates after the OID counter has wrapped around. However, up to now we used SnapshotDirty when scanning

pgsql: Do not select new object OIDs that match recently-dead entries.

2018-04-11 Thread Tom Lane
Do not select new object OIDs that match recently-dead entries. When selecting a new OID, we take care to avoid picking one that's already in use in the target table, so as not to create duplicates after the OID counter has wrapped around. However, up to now we used SnapshotDirty when scanning

pgsql: Do not select new object OIDs that match recently-dead entries.

2018-04-11 Thread Tom Lane
Do not select new object OIDs that match recently-dead entries. When selecting a new OID, we take care to avoid picking one that's already in use in the target table, so as not to create duplicates after the OID counter has wrapped around. However, up to now we used SnapshotDirty when scanning

pgsql: Do not select new object OIDs that match recently-dead entries.

2018-04-11 Thread Tom Lane
Do not select new object OIDs that match recently-dead entries. When selecting a new OID, we take care to avoid picking one that's already in use in the target table, so as not to create duplicates after the OID counter has wrapped around. However, up to now we used SnapshotDirty when scanning