KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com> wrote:
> > Can we remove such path and raise an error instead?
> > Also, even if we support the older servers in the routine,
> > the new bytea format will be another problem anyway.
> OK, I'll fix it.
I think we might need to discuss about explicit version checks in pg_restore.
It is not related with large objects, but with pg_restore's capability.
We've not supported to restore a dump to older servers, but we don't have any
version checks, right? Should we do the checks at the beginning of restoring?
If we do so, LO patch could be more simplified.
> The --schema-only with large objects might be unnatural, but the
> --data-only with properties of large objects are also unnatural.
> Which behavior is more unnatural?
I think large object metadata is a kind of row-based access controls.
How do we dump and restore ACLs per rows when we support them for
normal tables? We should treat LO metadata as same as row-based ACLs.
In my opinion, I'd like to treat them as part of data (not of schema).
NTT Open Source Software Center
In response to
pgsql-hackers by date
|Next:||From: Takahiro Itagaki||Date: 2010-02-02 00:45:19|
|Subject: Re: New VACUUM FULL crashes on temp relations|
|Previous:||From: Tom Lane||Date: 2010-02-02 00:09:12|
|Subject: Re: Make TOAST_TUPLES_PER_PAGE configurable per table. |