| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Petr Jelinek <petr(at)2ndquadrant(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Steve Singer <steve(at)ssinger(dot)info>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Subject: | Re: Replication identifiers, take 4 |
| Date: | 2015-04-08 04:59:46 |
| Message-ID: | CAB7nPqQt3g_wvPNOb5SYnYVBF0v=4AJO5w3+hnZg5iU-eGKWSA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 7, 2015 at 11:37 PM, Andres Freund <andres(at)anarazel(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2015-04-08 05:06:42 | Re: pg_dump / copy bugs with "big lines" ? |
| Previous Message | Jim Nasby | 2015-04-08 04:50:29 | Re: Really bad blowups with hash outer join and nulls |