From: | "Harald Armin Massa" <haraldarminmassa(at)gmail(dot)com> |
---|---|
To: | "Andrew Sullivan" <ajs(at)crankycanuck(dot)ca>, pgsql-general(at)postgresql(dot)org |
Subject: | large objects,was: Restoring 8.0 db to 8.1 |
Date: | 2008-01-08 15:01:45 |
Message-ID: | 7be3f35d0801080701n345c067dwd679cd0631b78fb4@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> 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 ....
Harald
--
GHUM Harald Massa
persuadere et programmare
Harald Armin Massa
Spielberger Straße 49
70435 Stuttgart
0173/9409607
fx 01212-5-13695179
-
EuroPython 2008 will take place in Vilnius, Lithuania - Stay tuned!
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2008-01-08 15:13:29 | Re: large objects,was: Restoring 8.0 db to 8.1 |
Previous Message | Harald Armin Massa | 2008-01-08 14:56:11 | Re: Create Index (Hash) on a Large Table Taking Days... |