Florian G. Pflug wrote:
I'm not really a tsearch user (just played with it a bit once). But I
wondered if you are aware that you can prevent certain objects from
being restored
quite easiy if you use pg_dump and pg_restore together with "custom
format" (-Fc). There is some option to pg_restore that reads the dump,
and ouputs a table of contents. You can then remove some entries from
that list, and pass the modified list to pg_restore which will skip
entries that do not show up on your modified list.
Maybe we could document some regexp, awk script, or similar that strips
the tsearch stuff from such a table of contents?
regards, Florian Pflug
This has worked well. I have a little sed script that deletes all the
tsearch2 looking stuff, then the restore works ok (except for the
trigger, which is ok).
However, am I safe not restoring all these operators?
1126; 2617 98028 OPERATOR public !! andy
1124; 2617 98024 OPERATOR public && andy
1112; 2617 98003 OPERATOR public < andy
1118; 2617 98017 OPERATOR public < andy
1113; 2617 98004 OPERATOR public <= andy
1119; 2617 98018 OPERATOR public <= andy
1117; 2617 98005 OPERATOR public <> andy
1123; 2617 98019 OPERATOR public <> andy
1128; 2617 98036 OPERATOR public <@ andy
1116; 2617 98006 OPERATOR public = andy
1122; 2617 98020 OPERATOR public = andy
1115; 2617 98001 OPERATOR public > andy
1121; 2617 98015 OPERATOR public > andy
1114; 2617 98002 OPERATOR public >= andy
1120; 2617 98016 OPERATOR public >= andy
1129; 2617 98039 OPERATOR public @ andy
1127; 2617 98037 OPERATOR public @> andy
1111; 2617 97955 OPERATOR public @@ andy
1110; 2617 97956 OPERATOR public @@ andy
1132; 2617 98055 OPERATOR public @@@ andy
1131; 2617 98056 OPERATOR public @@@ andy
1109; 2617 97941 OPERATOR public || andy
1125; 2617 98026 OPERATOR public || andy
1130; 2617 98038 OPERATOR public ~ andy
the operator = is not the 'normal =' is it? Its the 'tsearch2 =', right?
Do I need to worry about sed with window's users?
-Andy
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
