Обсуждение: Re: pgsql: Make LC_COLLATE and LC_CTYPE database-level settings.
heikki@postgresql.org (Heikki Linnakangas) writes: > Log Message: > ----------- > Make LC_COLLATE and LC_CTYPE database-level settings. Collation and > ctype are now more like encoding, stored in new datcollate and datctype > columns in pg_database. > > This is a stripped-down version of Radek Strnad's patch, with further > changes by me. > pgsql/src/bin/pg_dump: > pg_dump.c (r1.500 -> r1.501) > (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_dump.c?r1=1.500&r2=1.501) > pg_dumpall.c (r1.106 -> r1.107) > (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_dumpall.c?r1=1.106&r2=1.107) Let me report a problem with this... Running pg_dump encounters the following: chris@dba2:Slony-I/CMD/slony1-HEAD/tests> pg_dump -s slonyregress1 pg_dump: column number -1 is out of range 0..7 pg_dump: column number -1 is out of range 0..7 zsh: segmentation fault pg_dump -s slonyregress1 It's not a Slony-I-related issue; I get identical behaviour with other databases that do not have Slony-I in place. Things "seem to work" if I roll back this patch to pg_dump.c. So something's up... -- (reverse (concatenate 'string "moc.enworbbc" "@" "enworbbc")) http://www3.sympatico.ca/cbbrowne/emacs.html "Being really good at C++ is like being really good at using rocks to sharpen sticks." -- Thant Tessman
Chris Browne wrote: > Let me report a problem with this... > > Running pg_dump encounters the following: > > chris@dba2:Slony-I/CMD/slony1-HEAD/tests> pg_dump -s slonyregress1 > pg_dump: column number -1 is out of range 0..7 > pg_dump: column number -1 is out of range 0..7 > zsh: segmentation fault pg_dump -s slonyregress1 Thanks, fixed. I changed the column names from "collate" and "ctype" to "datcollate" and "datctype" at the last minute, and clearly didn't test pg_dump after that. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com