Re: libpq version in rpm packages

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

On Wed, 9 Nov 2005, Brian Mathis wrote:

> I noticed that the x86_64 version of the compat libs installs the files in
> /usr/lib, while the x86_64 postgresql-libs rpm uses /usr/lib64. Is there are
> reason for that? Otherwise, I'd prefer to keep all the 64bit libs in lib64.

Good catch! It seems that I used an errorneus .rpmmacros file in the
x86_64 server :(

The RPM is fixed now and will be uploaded in an hour. Until then, you can
do a

rpmbuild --rebuild

with the srpm and build the correct RPM for yourself.

Regards,
- --
Devrim GUNDUZ
Kivi Bilişim Teknolojileri - http://www.kivi.com.tr
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.gunduz.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDcl5S4zE8DGqpiZARAn/PAJ9zsfpK7Z85fMgGzqB8nedmiYFCswCgkyWU
H9nHr7MruNoResv+S8YBWdU=
=MfHS
-----END PGP SIGNATURE-----
>From pgsql-general-owner(at)postgresql(dot)org Wed Nov 9 17:00:46 2005
X-Original-To: pgsql-general-postgresql(dot)org(at)localhost(dot)postgresql(dot)org
Received: from localhost (av.hub.org [200.46.204.144])
by svr1.postgresql.org (Postfix) with ESMTP id A5273D77CC
for <pgsql-general-postgresql(dot)org(at)localhost(dot)postgresql(dot)org>; Wed, 9 Nov 2005 16:56:28 -0400 (AST)
Received: from svr1.postgresql.org ([200.46.204.71])
by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
with ESMTP id 84909-06
for <pgsql-general-postgresql(dot)org(at)localhost(dot)postgresql(dot)org>;
Wed, 9 Nov 2005 20:56:25 +0000 (GMT)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from floppy.pyrenet.fr (floppy.pyrenet.fr [194.116.145.2])
by svr1.postgresql.org (Postfix) with ESMTP id B31AFDA282
for <pgsql-general(at)postgresql(dot)org>; Wed, 9 Nov 2005 16:56:25 -0400 (AST)
Received: by floppy.pyrenet.fr (Postfix, from userid 106)
id B5A1A31058; Wed, 9 Nov 2005 21:56:26 +0100 (MET)
From: "Andrus" <eetasoft(at)online(dot)ee>
X-Newsgroups: pgsql.general
Subject: Re: Best way to use indexes for partial match at beginning
Date: Wed, 9 Nov 2005 22:46:27 +0200
Organization: Hub.Org Networking Services
Lines: 34
Message-ID: <dktnpk$2jrl$1(at)news(dot)hub(dot)org>
References: <dklr9d$781$1(at)news(dot)hub(dot)org> <20051108194837(dot)GO19551(at)pervasive(dot)com> <dksjma$2pkc$1(at)news(dot)hub(dot)org> <20051109110116(dot)GC21585(at)svana(dot)org> <dktj18$1buk$1(at)news(dot)hub(dot)org> <437251A3(dot)9000707(at)archonet(dot)com>
X-Complaints-To: usenet(at)news(dot)hub(dot)org
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
X-RFC2646: Format=Flowed; Response
To: pgsql-general(at)postgresql(dot)org
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=0.526 required=5 tests=[AWL=0.526]
X-Spam-Score: 0.526
X-Spam-Level:
X-Archive-Number: 200511/495
X-Sequence-Number: 86639

>> CREATE INDEX i1 ON foo(col1);
>>
>> cannot be used to optimize queries of type "get all rows where first n
>> charaters of col1 are known" in Postgres.
>
> Of course it will! Any btree based index will let you do that. Re-read the
> previous answers and make sure you pay attention to the bit about
> text_pattern_ops and LIKE in non-C locales.

Richard,

thank you. I try to formulate my problem more presicely.
I have table

CREATE TABLE foo ( bar CHAR(10) PRIMARY KEY);

Cluster locale is non-C. Database encoding is UTF-8. Postgres vers is 8.1

PRIMARY KEY clause creates btree based index so the index exists on bar.

I want to run fast queries by knowing first characters of bar like :

1. Select records from foo where first character of bar is A
2. Select records from foo where first character of bar is B
3. Select records from foo where first two characters of bar are BC
4. Select records from foo where first three characters of bar are ABC
etc.

Can you write sample WHERE clause which can use existing primary key index
for those queries ?

Andrus.