--- Scott Marlowe <[EMAIL PROTECTED]> wrote:
> On Wed, 2005-09-21 at 15:02, CSN wrote:
> > This appears related to my previous post:
> >
>
http://archives.postgresql.org/pgsql-general/2005-09/msg00809.php
> >
> > I setup a unique index using the title, yield, and
> > directions fields. Some ins
On Wed, 2005-09-21 at 15:02, CSN wrote:
> This appears related to my previous post:
> http://archives.postgresql.org/pgsql-general/2005-09/msg00809.php
>
> I setup a unique index using the title, yield, and
> directions fields. Some inserts are causing this
> error:
>
> DBD::Pg::st execute failed
Dan Armbrust wrote:
I'm trying to load some data into PostgreSQL 8.0.3, and I got the
error message "index row size 2904 exceeds btree maximum, 2713".
After a bunch of searching, I believe that I am getting this error
because a value that I am indexing is longer than ~ 1/3 of the block
size
Scott Marlowe <[EMAIL PROTECTED]> writes:
> On Tue, 2005-07-19 at 10:25, Tom Lane wrote:
>> None of the index types support entries larger than BLOCKSIZE-less-a-bit,
>> so switching to a different index type won't do more than push the
>> problem out by a factor of about 3.
> Are they compressed?
On Tue, 2005-07-19 at 10:25, Tom Lane wrote:
> Scott Marlowe <[EMAIL PROTECTED]> writes:
> > On Tue, 2005-07-19 at 05:42, Dennis Bjorklund wrote:
> >> You can index text fields, but you can't insert values bigger then
> >> BLOCKSIZE/3 when you have an index on that column.]
>
> > Please note that
Scott Marlowe <[EMAIL PROTECTED]> writes:
> On Tue, 2005-07-19 at 05:42, Dennis Bjorklund wrote:
>> You can index text fields, but you can't insert values bigger then
>> BLOCKSIZE/3 when you have an index on that column.]
> Please note that the size limitation is for btree indexes, the most
> com
On Tue, 2005-07-19 at 05:42, Dennis Bjorklund wrote:
> On Mon, 18 Jul 2005, Jaime Casanova wrote:
>
> > I don't think you could create indexes on text fields... there are
> > other type of indexes for that... tsearch2 for example
>
> You can index text fields, but you can't insert values bigger t
On Mon, 18 Jul 2005, Jaime Casanova wrote:
> I don't think you could create indexes on text fields... there are
> other type of indexes for that... tsearch2 for example
You can index text fields, but you can't insert values bigger then
BLOCKSIZE/3 when you have an index on that column.
--
/Den
> The index that is failing is CREATE INDEX i1 ON conceptproperty USING btree
> (codingschemename, property, propertyvalue).
>
I don't think you could create indexes on text fields... there are
other type of indexes for that... tsearch2 for example
--
Atentamente,
Jaime Casanova
(DBA: DataBase
> I'm trying to load some data into PostgreSQL 8.0.3, and I got the error
> message "index row size 2904 exceeds btree maximum, 2713". After a
> bunch of searching, I believe that I am getting this error because a
> value that I am indexing is longer than ~ 1/3 of the block size - or the
> BLCKSZ
Dan Armbrust <[EMAIL PROTECTED]> writes:
> The index that is failing is CREATE INDEX i1 ON conceptproperty USING
> btree (codingschemename, property, propertyvalue).
>
> Usually, the 'propertyValue' field is fairly short - 100 chars or
> less. And in those cases, I need to be able to do an indexe
Dan Armbrust wrote:
Hmm, well, I don't know if it is actually building an index properly on
this column, I just assumed that it was. It doesn't fail on every
insert, only on the one that has a really long text value. I know it
doesn't use the index when I do "ILIKE" queries, resulting in poor
On Mon, Jul 18, 2005 at 14:44:26 -0500,
Dan Armbrust <[EMAIL PROTECTED]> wrote:
> I'm trying to load some data into PostgreSQL 8.0.3, and I got the error
> message "index row size 2904 exceeds btree maximum, 2713". After a
> bunch of searching, I believe that I am getting this error because a
Dan Armbrust <[EMAIL PROTECTED]> writes:
> All of my other limitations on changing things aside - given a query
> like this:
>
> Select * from conceptproperty where codingSchemeName='foo' AND
> property='anotherfoo' and propertyValue ILIKE 'valu%'
>
> What indexe(s) would be recommended?
I'd index
Hmm, well, I don't know if it is actually building an index properly on
this column, I just assumed that it was. It doesn't fail on every
insert, only on the one that has a really long text value. I know it
doesn't use the index when I do "ILIKE" queries, resulting in poor
performance... but
On Mon, 2005-07-18 at 16:01, Dan Armbrust wrote:
> Hmm, well, I don't know if it is actually building an index properly
> on this column, I just assumed that it was. It doesn't fail on every
> insert, only on the one that has a really long text value. I know it
> doesn't use the index when I do "
On Mon, 2005-07-18 at 15:17, Dan Armbrust wrote:
> We have built a Model for terminologies that we call The Lexical Grid
> (more info http://informatics.mayo.edu/LexGrid/index.php)
>
> LexGrid has multiple backend data storage mechanisms, including LDAP
> and SQL. We do our best to remain impleme
We have built a Model for terminologies that we call The Lexical Grid
(more info http://informatics.mayo.edu/LexGrid/index.php)
LexGrid has multiple backend data storage mechanisms, including LDAP
and SQL. We do our best to remain implementation independent - our SQL
implementations, for exam
Nevermind this question...
>
Where is the documentation on tsearch2?
Google first, ask second, I remind myself again... I knew I hadn't
seen it mentioned in the official postgresql manual.. didn't think
about it being an extension.
Dan
Dan Armbrust wrote:
Hmm, well, I don't know if it
19 matches
Mail list logo
