| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bill Moran <wmoran(at)potentialtech(dot)com> |
| Cc: | Magnus Reftel <magnus(dot)reftel(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Thousands of users using one schema -> ERROR: row is too big |
| Date: | 2011-03-01 21:45:58 |
| Message-ID: | 27519.1299015958@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Bill Moran <wmoran(at)potentialtech(dot)com> writes:
> In response to Magnus Reftel <magnus(dot)reftel(at)gmail(dot)com>:
>> On IRC, linuxpoet and andres suggested that the problem is that the
> nspacl column in pg_catalog.pg_namespace grows too large. A suggested
> fix by linuxpoet adds a toast table to pg_namespace.
> I would think that a better solution would be to follow best practices and
> create roles and put users in those roles, so you don't have to have so
> many grants on objects.
Yeah. You could probably get around it with the add-a-toast-table hack,
but I think performance would be a lot worse.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2011-03-01 21:46:21 | #PgEast Training Schedule Up |
| Previous Message | Joshua D. Drake | 2011-03-01 21:18:38 | Re: Thousands of users using one schema -> ERROR: row is too big |