Security holes? Explain yourself please.
No ownership, and no permissions...
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.
I did have a plan to do this for 8.1, but so f
Christopher Kings-Lynne <[EMAIL PROTECTED]> 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
