andy wrote:
Is there any chance there is an easier way to backup/restore? On one
hand, its not too bad, and it'll only be once (correct?). Now that fts
is in core future backup/restores will work, right? I think it's
analogous to telling someone they are updating from tsearch2 to
tsearch3,
Andy,
seems you're a right person for writing migration guide.
Oleg
On Wed, 10 Oct 2007, andy wrote:
andy wrote:
Andy Colson wrote:
Hi All,
You knew it was coming
I tried doing a pg_dump --schema-only and restoring just that, but still
got a bunch of errors (those above). If I
Oleg Bartunov wrote:
Andy,
seems you're a right person for writing migration guide.
Oleg
On Wed, 10 Oct 2007, andy wrote:
Where would be an easy place to find all the renamed functions?
My experience with fts is limited to one project, and I just used all
the default dictionaries, so I've
Oleg Bartunov wrote:
Andy,
seems you're a right person for writing migration guide.
Oleg
On Wed, 10 Oct 2007, andy wrote:
Where would be an easy place to find all the renamed functions?
My experience with fts is limited to one project, and I just used all
the default dictionaries, so I've
andy wrote:
Is there any chance there is an easier way to backup/restore? On one
hand, its not too bad, and it'll only be once (correct?). Now that fts
is in core future backup/restores will work, right? I think it's
analogous to telling someone they are updating from tsearch2 to
tsearch3,
Florian G. Pflug wrote:
andy wrote:
Is there any chance there is an easier way to backup/restore? On one
hand, its not too bad, and it'll only be once (correct?). Now that
fts is in core future backup/restores will work, right? I think it's
analogous to telling someone they are updating
andy wrote:
Florian G. Pflug wrote:
Maybe we could document some regexp, awk script, or similar that
strips the tsearch stuff from such a table of contents?
Ahh, I did not know that... I'll try that out and see if I can come up
with something. Thanks!
If you hack the old tsearch2.sql
On Thu, 11 Oct 2007, andy wrote:
Oleg Bartunov wrote:
Andy,
seems you're a right person for writing migration guide.
Oleg
On Wed, 10 Oct 2007, andy wrote:
Where would be an easy place to find all the renamed functions?
My incomplete list:
On 10/11/07, Florian G. Pflug [EMAIL PROTECTED] wrote:
Maybe we could document some regexp, awk script, or similar that strips the
tsearch stuff from such a table of contents?
Just my .02c for those who will work on migration manual.
In my case, all tsearch2 stuff was kept (before 8.3) in
I working on binary compatible library with tsearch2, which should be
usable for all users who has default configuration of tsearch2. I
hope, I send patch before morning
Pavel
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
Nikolay Samokhvalov [EMAIL PROTECTED] writes:
During restoration to 8.3 I've catched segfaults -- during INSERTs
into tables with tsearch2.tsvector columns.
Segfaults? That shouldn't happen. Please show a test case.
regards, tom lane
---(end
Nikolay Samokhvalov [EMAIL PROTECTED] writes:
On 10/11/07, Tom Lane [EMAIL PROTECTED] wrote:
Segfaults? That shouldn't happen. Please show a test case.
Test case: use old tsearch2.so to register all tsearch2 functions to
tsearch2 schema (old fashioned way). Then try:
How did you get 8.3 to
On 10/11/07, Tom Lane [EMAIL PROTECTED] wrote:
Nikolay Samokhvalov [EMAIL PROTECTED] writes:
During restoration to 8.3 I've catched segfaults -- during INSERTs
into tables with tsearch2.tsvector columns.
Segfaults? That shouldn't happen. Please show a test case.
Test case: use old
On 10/11/07, Tom Lane [EMAIL PROTECTED] wrote:
Nikolay Samokhvalov [EMAIL PROTECTED] writes:
On 10/11/07, Tom Lane [EMAIL PROTECTED] wrote:
Segfaults? That shouldn't happen. Please show a test case.
Test case: use old tsearch2.so to register all tsearch2 functions to
tsearch2 schema
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
andy [EMAIL PROTECTED] writes:
the operator = is not the 'normal =' is it? Its the 'tsearch2 =', right?
That one probably is, but how is your sed script going to distinguish it
from other user-defined '=' operators that might be in the dump?
Do I need to worry about sed with window's users?
Tom Lane wrote:
andy [EMAIL PROTECTED] writes:
the operator = is not the 'normal =' is it? Its the 'tsearch2 =', right?
That one probably is, but how is your sed script going to distinguish it
from other user-defined '=' operators that might be in the dump?
Do I need to worry about sed
andy wrote:
Do I need to worry about sed with window's users?
yes.
Perl is probably more common in Windows, and should be able to do
everything sed can. It's also required for doing Windows/MSVC builds.
cheers
andrew
---(end of
Hi All,
You knew it was coming
I have an 8.2 database that has full text searching. I tried to
backup/restore it to 8.3 but got lots of errors:
snip
ERROR: could not access file $libdir/tsearch2: No such file or directory
ERROR: function public.gtsq_in(cstring) does not exist
ERROR:
Andy Colson wrote:
Hi All,
You knew it was coming
I tried doing a pg_dump --schema-only and restoring just that, but still
got a bunch of errors (those above). If I clean that up of all the old
text search stuff, and then run it, then do the data, will that work ok?
Further to
Andy Colson [EMAIL PROTECTED] writes:
I have an 8.2 database that has full text searching. I tried to
backup/restore it to 8.3 but got lots of errors:
...
I didn't really expect it to totally work, but I'm not sure how to move
my db.
Did the data transfer over? The declarations of the
Tom Lane wrote:
Andy Colson [EMAIL PROTECTED] writes:
I have an 8.2 database that has full text searching. I tried to
backup/restore it to 8.3 but got lots of errors:
...
I didn't really expect it to totally work, but I'm not sure how to move
my db.
Did the data transfer over? The
andy wrote:
Andy Colson wrote:
Hi All,
You knew it was coming
I tried doing a pg_dump --schema-only and restoring just that, but
still got a bunch of errors (those above). If I clean that up of all
the old text search stuff, and then run it, then do the data, will
that work ok?
andy [EMAIL PROTECTED] writes:
Tom Lane wrote:
Did the data transfer over? The declarations of the former contrib
functions would of course fail, but type tsvector is still there.
I would like to think that ignoring pg_restore's whining would get
you most of the way there.
So I tried
Tom Lane wrote:
andy [EMAIL PROTECTED] writes:
Tom Lane wrote:
Did the data transfer over? The declarations of the former contrib
functions would of course fail, but type tsvector is still there.
I would like to think that ignoring pg_restore's whining would get
you most of the way there.
Andy,
seems you're a right person for writing migration guide.
Oleg
On Wed, 10 Oct 2007, andy wrote:
andy wrote:
Andy Colson wrote:
Hi All,
You knew it was coming
I tried doing a pg_dump --schema-only and restoring just that, but still
got a bunch of errors (those above). If I
26 matches
Mail list logo
