Where do I find out how to compile and run PostgreSQL under WindowsNT?
Thought I saw something about pre-built binaries available somewhere.
Thanks
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://www.postgresql.org/sea
... however, if you want to do some of the legwork yourself, here are
the ideas I had about what to do:
pg_opclass should have, not just one row for each distinct opclass name,
but one row for each supported combination of index AM and opclass name.
Doing it this way would allow us to put additio
Oleg Bartunov <[EMAIL PROTECTED]> writes:
> Any chance you'd untie a knot for our development in 7.2 development
> cycle ?
I am trying to focus on getting concurrent VACUUM done, because I think
that's a "must do" for 7.2. I hope to have some time during August to
deal with your GIST issues, but
mlw <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>>> Passing listen(5) would probably be sufficient for Postgres.
>>
>> It demonstrably is not sufficient. Set it that way in pqcomm.c
>> and run the parallel regression tests. Watch them fail.
> That's interesting, I would not have guessed that
> We don't let people add columns to an existing index so I don't see why
> we should have EXTEND INDEX unless index twiddling is more common with
> partial indexes.
>
Nothing is common with partial indexes at the moment -- the feature is
not currently implemented, and I don't think other datab
On Fri, 13 Jul 2001, Tom Lane wrote:
> Since I am about to add a "bulk delete" routine to the index access
> method APIs for concurrent VACUUM, I need to add a column to pg_am
> to define the associated procedure for each index AM. This seems like
> a fine time to clean up some of the other outs
Tom Lane wrote:
>
> mlw <[EMAIL PROTECTED]> writes:
> > Nathan Myers wrote:
> >> But using SOMAXCONN blindly is always wrong; that is often 5, which
> >> is demonstrably too small.
>
> > It is rumored that many BSD version are limited to 5.
>
> BSD systems tend to claim SOMAXCONN = 5 in the hea
