large objects,was: [GENERAL] Restoring 8.0 db to 8.1
> 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! ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: large objects,was: [GENERAL] Restoring 8.0 db to 8.1
On Jan 8, 2008 9:01 AM, Harald Armin Massa <[EMAIL PROTECTED]> 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. ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: large objects,was: [GENERAL] Restoring 8.0 db to 8.1
On Jan 8, 2008, at 9:13 AM, Scott Marlowe wrote: On Jan 8, 2008 9:01 AM, Harald Armin Massa <[EMAIL PROTECTED]> 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. Also, with bytea (and any other varying length data type) there is still a limit of 1G via TOASTing. Large Objects will get you up to 2G for one field. Erik Jones DBA | Emma® [EMAIL PROTECTED] 800.595.4401 or 615.292.5888 615.292.0777 (fax) Emma helps organizations everywhere communicate & market in style. Visit us online at http://www.myemma.com ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org/
