Re: large objects,was: Restoring 8.0 db to 8.1
От | Scott Marlowe |
---|---|
Тема | Re: large objects,was: Restoring 8.0 db to 8.1 |
Дата | |
Msg-id | dcc563d10801080713g1740365etf3d50ae061d34ceb@mail.gmail.com обсуждение исходный текст |
Ответ на | large objects,was: Restoring 8.0 db to 8.1 ("Harald Armin Massa" <haraldarminmassa@gmail.com>) |
Ответы |
Re: large objects,was: Restoring 8.0 db to 8.1
|
Список | pgsql-general |
On Jan 8, 2008 9:01 AM, Harald Armin Massa <haraldarminmassa@gmail.com> wrote: > > Not likely to change in the future, no. Slony uses triggers to manage the > > changed rows. We can't fire triggers on large object events, so there's no > > way for Slony to know what happened. > > that leads me to a question I often wanted to ask: > > is there any reason to create NEW PostgreSQL databases using Large > Objects, now that there is bytea and TOAST? (besides of legacy needs) > > as much as I read, they take special care in dump/restore; force the > use of some special APIs on creating, do not work with Slony .... The primary advantage of large objects is that you can read like byte by byte, like a file.
В списке pgsql-general по дате отправления: