[BUGS] BUG #3798: Add fuzzy string search in TSearch2

2007-12-04 Thread Rikardo Tinauer
The following bug has been logged online: Bug reference: 3798 Logged by: Rikardo Tinauer Email address: [EMAIL PROTECTED] PostgreSQL version: 8.3 Operating system: All Description:Add fuzzy string search in TSearch2 Details: This is not really a bug but just an idea

Re: [BUGS] BUG #3798: Add fuzzy string search in TSearch2

2007-12-04 Thread Stefan Kaltenbrunner
Rikardo Tinauer wrote: > The following bug has been logged online: > > Bug reference: 3798 > Logged by: Rikardo Tinauer > Email address: [EMAIL PROTECTED] > PostgreSQL version: 8.3 > Operating system: All > Description:Add fuzzy string search in TSearch2 > Details: >

Re: [BUGS] BUG #3750: Invalid frontend message type 112

2007-12-04 Thread Magnus Hagander
On Fri, Nov 16, 2007 at 06:31:43AM +0100, Christian Ullrich wrote: > * Magnus Hagander wrote: > > >Christian Ullrich wrote: > > >>psql tells me about an "invalid frontend message type 112". Most of the > >>time, that error comes as the first line of output from psql (above the > >>"Welcome to" li

Re: [BUGS] BUG #3790: pg_restore error canceling statement due touser request

2007-12-04 Thread Tom Lane
Gregory Stark <[EMAIL PROTECTED]> writes: > I guess we should capture this error with a PG_TRY and silently abort instead. > Just a NOTICE or INFO should be sufficient. Other errors should of course be > rethrown. This falls in the category of "destabilizing the code for purely cosmetic reasons",

Re: [BUGS] BUG #3790: pg_restore error canceling statement due touser request

2007-12-04 Thread Gregory Stark
"Tom Lane" <[EMAIL PROTECTED]> writes: > This falls in the category of "destabilizing the code for purely > cosmetic reasons", and would be a foolish change to make at RC1 time. I suppose. Expect to have more bug reports like this one then though. > We could change the text of the ERROR message

Re: [BUGS] BUG #3790: pg_restore error canceling statement due touser request

2007-12-04 Thread Alvaro Herrera
Gregory Stark escribió: > "Tom Lane" <[EMAIL PROTECTED]> writes: > > > This falls in the category of "destabilizing the code for purely > > cosmetic reasons", and would be a foolish change to make at RC1 time. > > I suppose. Expect to have more bug reports like this one then though. > > > We cou

Re: [BUGS] BUG #3790: pg_restore error canceling statement due to user request

2007-12-04 Thread Bruce Momjian
Alvaro Herrera wrote: > Bruce Momjian escribi??: > > Magnus Hagander wrote: > > > On Fri, Nov 30, 2007 at 10:13:53AM +, Gregory Stark wrote: > > > > > > > > "Mike C." <[EMAIL PROTECTED]> writes: > > > > > > > > > I don't know if this is either a wording change, or a more serious > > > > > bu

Re: [BUGS] BUG #3790: pg_restore error canceling statement due to user request

2007-12-04 Thread Alvaro Herrera
Bruce Momjian escribió: > Alvaro Herrera wrote: > Ah, OK. Right now we have these two cancel messages: > > if (cancel_from_timeout) > ereport(ERROR, > (errcode(ERRCODE_QUERY_CANCELED), > errmsg("canceling statement due to statement tim

Re: [BUGS] Test suite fails on alpha architecture

2007-12-04 Thread Martin Pitt
Hi, Tom Lane [2007-11-07 13:49 -0500]: > All the other diffs that Martin showed are divide-by-zero failures, > and I do not see any of them on Gentoo's machine. I think that this > must be a compiler bug. The first example in his diffs is just > "select 1/0", which executes this code: > > i

Re: [BUGS] Test suite fails on alpha architecture

2007-12-04 Thread Martin Pitt
Martin Pitt [2007-12-04 23:43 +0100]: > So I tried to approach it from the other side: Building postgresql > with CFLAGS="-O0 -g" or "-O1 -g" works correctly, but with "-O2 -g" I > get above bug. Just FAOD, building with gcc 4.1 and -O2 works fine. I guess this sufficiently proves that this is a g

Re: [BUGS] BUG #3790: pg_restore error canceling statement due touser request

2007-12-04 Thread Tom Lane
Alvaro Herrera <[EMAIL PROTECTED]> writes: > I don't advocate changing that ERROR to anything else. The message > wording, as Tom says, can easily be changed -- I think this patch should > be enough. Feel free to propose better wording. Minor gripe: all three variants of the message should follo