Re: Disable large objects GUC
| От | Tom Lane |
|---|---|
| Тема | Re: Disable large objects GUC |
| Дата | |
| Msg-id | 17727.1114575586@sss.pgh.pa.us обсуждение |
| Ответ на | Disable large objects GUC (Christopher Kings-Lynne <chriskl@familyhealth.com.au>) |
| Ответы |
Re: Disable large objects GUC
|
| Список | pgsql-hackers |
Christopher Kings-Lynne <chriskl@familyhealth.com.au> writes:
> I wonder if there's any use for an allow_large_objects = true/false GUC
> parameter?
> It'd be nice to be able to switch it off as part of site policy so that
> the security holes in it aren't able to be exposed, plus you can
> guarantee as the site admin that pg_dumpall will produce a complete
> dump.
Security holes? Explain yourself please.
As for the latter point, ISTM the todo item is "fix pg_dumpall" more
than "eliminate large objects". Certainly the fix isn't easy, but
that isn't an argument to cut and run.
regards, tom lane
В списке pgsql-hackers по дате отправления: