-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Nov 12, 2006 at 04:49:33PM +, Basil Evseenko wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2755
[...]
> # \d tables.cart
[no cart_id field]
> # \d tables.download
[cart_id field]
> # SELECT count(1) from t
Tom Lane wrote:
> While there's not anything wrong with this proposed patch in itself,
> I have to admit that I don't see the point.
The points are:
1. It is just unpleasant to leave the overflow.
2. It is not easy for users to understand what they should do when they
encounter the error messag
The following bug has been logged online:
Bug reference: 2754
Logged by: Roman Shterenzon
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3
Operating system: RHEL3
Description:cache lookup failed for function 8470229
Details:
We receive:
"ERROR: cache looku
The following bug has been logged online:
Bug reference: 2755
Logged by: Basil Evseenko
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: Linux 2.6
Description:strange select behavior
Details:
# \d tables.cart
Column| Typ
> > no, i used the win32 setup and selected to install tsearch2 contrib
> > module... so i didn't even had to run "\i tsearch2.sql".
> installation
> > logs are available if helpful.
>
> Hm, I wonder whether the windows installer changes tsearch2's
> configuration at all.
It doesn't. And in m
Tom Lane wrote:
"Thomas H." <[EMAIL PROTECTED]> writes:
no, i used the win32 setup and selected to install tsearch2 contrib
module... so i didn't even had to run "\i tsearch2.sql". installation logs
are available if helpful.
Hm, I wonder whether the windows installer changes tsearch2's
config
it should... at least for <8.2 this worked fine without manually installing
tsearch2. the tsearch2.sql is run by the installer, the tsearch2 objects are
present in template1 and thus in the freshly created db. also the function
and types are there or else the table creation would fail in first p
"Thomas H." <[EMAIL PROTECTED]> writes:
> no, i used the win32 setup and selected to install tsearch2 contrib
> module... so i didn't even had to run "\i tsearch2.sql". installation logs
> are available if helpful.
Hm, I wonder whether the windows installer changes tsearch2's
configuration at al
Did you do anything to install tsearch2 into this fresh database beyond
"\i tsearch2.sql"?
no, i used the win32 setup and selected to install tsearch2 contrib
module... so i didn't even had to run "\i tsearch2.sql". installation logs
are available if helpful.
should i try a manual install of
"Thomas H." <[EMAIL PROTECTED]> writes:
> here are the steps to reproduce:
>
> 1. intall win32 beta3 as new instance using UTF8 / en_US and tsearch2
> module, everything else default
> 2. create new db with encoding UTF8, standard template
> 3. load data from http://alternize.com/pgsql/ts
here are the steps to reproduce:
1. intall win32 beta3 as new instance using UTF8 / en_US and tsearch2
module, everything else default
2. create new db with encoding UTF8, standard template
3. load data from http://alternize.com/pgsql/tsearch2test.zip (updated dump
so it only includes
yeah... i dont think it will be related to index anyway.
it looks to me that some extra bytes are written to the allocated
memory when locale is set to en-US etc. The warning
"WARNING: detected write past chunk end in ExprContext 02C6D0F8"
is generated when you write bytes on a location more th
Ok, I've run this test on an assert enabled build (my msvc build,
actually, so I could get a debugger on it if needed). It then outputs:
WARNING: detected write past chunk end in ExprContext 02C6D0F8
WARNING: detected write past chunk end in ExprContext 02C6AEA0
WARNING: detected write past chu
this bug (please see below) is unfortunately still present in beta3 (win32
build). test case still crashes the child process and lets postmaster kill &
reload everything.
it is not GiST-related, i've just validated the same problem using GIN.
this breaks tsearch2 functionality on our win32 sys
14 matches
Mail list logo
