Thread: Re: Index Anding

Re: Index Anding

From
Andrew Sullivan
Date:
You probably want to take these questions to the -general list, or
-admin, in future.  That said. . .

On Wed, Jan 31, 2007 at 08:56:21AM -0600, Hiltibidal, Robert wrote:
> 
> Does postgres provide for index anding? 

Yes.  See
<http://www.postgresql.org/docs/8.2/static/indexes-bitmap-scans.html>. 
You don't need to do anything special.

> How does postgres handle tablespaces? I currently have my indexes going
> to one table space with my data going to a different table space. Is
> this possible in postgres?

Yes.  See
<http://www.postgresql.org/docs/8.2/static/manage-ag-tablespaces.html>

> Does postgres provide 64 bit support? If so is there a precompiled 64
> bit version for AIX? I have the 32 bit GCC and can compile 32 bit. 64
> bit GCC I have not gotten stabilized. (I cold use a tip in that
> direction if anyone lese has experienced similar issues)  

I know we've managed to get it to work using gcc, but I haven't had  
to do it in a while (ask on -general or -admin, I suggest).  More
important is to make sure you tell the compiler to use all the
memory.  For reasons that are completely beyond my ken, AIX imposes a 
memory limitation on every program at compile time.  There are some  
hints about this in the FAQ_AIX.

A

-- 
Andrew Sullivan  | ajs@crankycanuck.ca
When my information changes, I alter my conclusions.  What do you do sir?    --attr. John Maynard Keynes


Re: Index Anding

From
Chris Browne
Date:
ajs@crankycanuck.ca (Andrew Sullivan) writes:
>> Does postgres provide 64 bit support? If so is there a precompiled 64
>> bit version for AIX? I have the 32 bit GCC and can compile 32 bit. 64
>> bit GCC I have not gotten stabilized. (I cold use a tip in that
>> direction if anyone lese has experienced similar issues)  
>
> I know we've managed to get it to work using gcc, but I haven't had
> to do it in a while (ask on -general or -admin, I suggest).  More
> important is to make sure you tell the compiler to use all the
> memory.  For reasons that are completely beyond my ken, AIX imposes
> a memory limitation on every program at compile time.  There are
> some hints about this in the FAQ_AIX.

Here's the environment data submitted to ./configure for a recent build of 8.1.5:
pgdba@ydb1 $ ./pg_config --configure '--prefix=/where/I/stow/it '--enable-thread-safety' '--enable-debug'
'--with-libraries=/opt/freeware/lib''--with-includes=/opt/freeware/include' 'CC=gcc -maix64'
'LDFLAGS=-Wl,-bmaxdata:0x80000000,-bbigtoc'

Note that you also need to export:
export OBJECT_MODE=64

And you need to make sure that you are using the AIX ld, and not GNU ld...

For version 7.4, it was considerably fiddlier to do a build.  For 8.2,
it is neither overly baroque nor overly unpleasant, which I consider a
direct result of the combination of Seneca Cunningham's reports to
-hackers/-ports as well as BuildFarm runs...
-- 
(reverse (concatenate 'string "ofni.sesabatadxunil" "@" "enworbbc"))
http://cbbrowne.com/info/finances.html
Rules  of the  Evil  Overlord #30.   "All  bumbling conjurers,  clumsy
squires, no-talent  bards, and  cowardly thieves in  the land  will be
preemptively put  to death.  My foes  will surely give  up and abandon
their quest if they have no source of comic relief."
<http://www.eviloverlord.com/>