Обсуждение: Can't load a 7.3.4 dump into 7.4CVS
I tried(!) to load my 7.3.4 data into 7.4CVS. the Bricolage folks have managed to make a circular definition (at least not loadable). why does each setval() call invoke the pager? the dump I used is at: http://www.lerctr.org/~ler/pg.dump.gz $ ls -l pg.dump* -rw-r--r-- 1 ler isis 10989689 Aug 9 11:43 pg.dump.gz $ you need to have contrib/dbsize, contrib/pgstattuple, contrib/tsearch, contrib/dblink installed. Any ideas, folks? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: ler@lerctr.org US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
--On Saturday, August 09, 2003 11:47:43 -0500 Larry Rosenman <ler@lerctr.org> wrote: > I tried(!) to load my 7.3.4 data into 7.4CVS. > > the Bricolage folks have managed to make a circular definition (at least > not loadable). > > why does each setval() call invoke the pager? > > the dump I used is at: > > http://www.lerctr.org/~ler/pg.dump.gz > > $ ls -l pg.dump* > -rw-r--r-- 1 ler isis 10989689 Aug 9 11:43 pg.dump.gz > $ > > you need to have contrib/dbsize, contrib/pgstattuple, contrib/tsearch, > contrib/dblink installed. > > Any ideas, folks? The load output is at: http://www.lerctr.org/~ler/pg734.load.gz $ ls -l pg734.load.gz -rw-r--r-- 1 ler isis 216248 Aug 9 12:25 pg734.load.gz $ -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: ler@lerctr.org US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
--On Saturday, August 09, 2003 12:26:06 -0500 Larry Rosenman <ler@lerctr.org> wrote: > > > --On Saturday, August 09, 2003 11:47:43 -0500 Larry Rosenman > <ler@lerctr.org> wrote: > >> I tried(!) to load my 7.3.4 data into 7.4CVS. >> >> the Bricolage folks have managed to make a circular definition (at least >> not loadable). >> >> why does each setval() call invoke the pager? >> >> the dump I used is at: >> >> http://www.lerctr.org/~ler/pg.dump.gz >> >> $ ls -l pg.dump* >> -rw-r--r-- 1 ler isis 10989689 Aug 9 11:43 pg.dump.gz >> $ >> >> you need to have contrib/dbsize, contrib/pgstattuple, contrib/tsearch, >> contrib/dblink installed. >> >> Any ideas, folks? > The load output is at: > > http://www.lerctr.org/~ler/pg734.load.gz > $ ls -l pg734.load.gz > -rw-r--r-- 1 ler isis 216248 Aug 9 12:25 pg734.load.gz > $ Another issue: plpgsql.so needs the elog() function, but it's not exported... LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: ler@lerctr.org US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
--On Saturday, August 09, 2003 12:31:06 -0500 Larry Rosenman <ler@lerctr.org> wrote: > Another issue: plpgsql.so needs the elog() function, but it's not > exported... actually, this is because of a hardcoded path in my old db, it was picking up the 7.3.4 plpgsql.so. > > LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: ler@lerctr.org US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
On Sat, 9 Aug 2003, Larry Rosenman wrote: > I tried(!) to load my 7.3.4 data into 7.4CVS. > > the Bricolage folks have managed to make a circular definition (at least > not loadable). > > why does each setval() call invoke the pager? > > the dump I used is at: > > http://www.lerctr.org/~ler/pg.dump.gz > > $ ls -l pg.dump* > -rw-r--r-- 1 ler isis 10989689 Aug 9 11:43 pg.dump.gz > $ > > you need to have contrib/dbsize, contrib/pgstattuple, contrib/tsearch, > contrib/dblink > installed. > > Any ideas, folks? Unfortunately this looks like a case that the dump needs to be edited for to move the constraint into an ALTER TABLE ADD CONSTRAINT after the function is defined. In general, this looks like one of those things that will eventually be fixed by ordering the dumped objects by dependencies. In general, check constraints that call functions that do subselects (to get around the check constraint limitations currently) can be problematic because they don't actually make a strong constraint and can get you into situations that are not reloadable even if we ordered all the objects correctly without knowing more than the current state of the data in the table.