Re: Replication identifiers, take 4 - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Replication identifiers, take 4
Date
Msg-id CAB7nPqQt3g_wvPNOb5SYnYVBF0v=4AJO5w3+hnZg5iU-eGKWSA@mail.gmail.com
Whole thread Raw
In response to Re: Replication identifiers, take 4  (Andres Freund <andres@anarazel.de>)
Responses Re: Replication identifiers, take 4
List pgsql-hackers
On Tue, Apr 7, 2015 at 11:37 PM, Andres Freund <andres@anarazel.de> wrote:
> On 2015-04-07 16:30:25 +0200, Andres Freund wrote:
>> And with temp tables (or much more extremely WITH OID tables)
>> and such it's not that hard to reach that point.
>
> Oh, and obviously toast data. A couple tables with toasted columns is
> also a good way to rapidly consume oids.

You are forgetting as well large objects on the stack, when client
application does not assign an OID by itself.
-- 
Michael



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: Really bad blowups with hash outer join and nulls
Next
From: Jim Nasby
Date:
Subject: Re: pg_dump / copy bugs with "big lines" ?