Hi all, just a little thing. Couldn't see this mentioned here
(http://gborg.postgresql.org/project/slony1/bugs/buglist.php) or when I
googled, so...
My DB contains tables whose names are all upper-case, e.g.:
CREATE TABLE ACCOUNT
( );
slon_tools.conf has the same:
"pkeyedtables" => [
'ACCOUNT',
Then created slonik script to create the set:
slonik_create_set --config /etc/slon_tools.conf 1 > create_set.slnk
But when you run that script it fails:
$ slonik <create_set.slnk
<stdin>:16: Subscription set 1 created
<stdin>:17: Adding tables to the subscription set
<stdin>:18: PGRES_FATAL_ERROR select
"_vtud_replication".determineIdxnameUnique('public.ACCOUNT', NULL); - ERROR:
Slony-I: table "public"."ACCOUNT" not found
The issue appears to be that PostgreSQL is folding ACCOUNT -> account, but the
Slony function to determine unique index does not do the same:
vtud=# select
"_vtud_replication".determineIdxnameUnique('public.ACCOUNT',NULL);
ERROR: Slony-I: table "public"."ACCOUNT" not found
vtud=# select
"_vtud_replication".determineIdxnameUnique('public.account',NULL);
determineidxnameunique
------------------------
pk_account
(1 row)
The work-around was to lower-case all object names in slon_tools.conf, and
after that is works fine. The solution (I guess) is to make
determineIdxnameUnique do a case-insensitive query on object name.
Has this been found/discussed/resolved?
Regards, Philip.
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
-----------------
Utiba Pty Ltd
This message has been scanned for viruses and
dangerous content by Utiba mail server and is
believed to be clean.
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general
