Current content of control file is insufficient to check if database is
compatible with postgres server. I think we should create footprint file which
will contains all page data structures and their member offset and length (and
maybe more).
As a first step which is useful at least for in-pla
Just realized that I forgot to add the DROP FUNCTION statements to the
uninstall script. New patch attached.
Best,
David
citext_casting2.patch.gz
Description: GNU Zip compressed data
On Jul 31, 2008, at 10:42, David E. Wheeler wrote:
On Jul 30, 2008, at 13:10, Tom Lane wrote:
Yes, th
"Steve Mitchell" <[EMAIL PROTECTED]> wrote:
> Do we need a new API (ambulkinsert) to support optimized bulk insertion
> into indexes?
Do you have a concrete image of ambulkinsert? I think we need to bring out
the bottleneck of current insertion method first, before writing codes.
Finding keys or
Tom Lane napsal(a):
Alvaro Herrera <[EMAIL PROTECTED]> writes:
I wonder if we can do something diffie-hellman'ish, where we have a
parameter exchanged in the initial SSL'ed handshake, which is later used
to generate new cancel keys each time the previous one is used.
Seems like the risk of get
> "Tom" == Tom Lane <[EMAIL PROTECTED]> writes:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
>> I wonder if we can do something diffie-hellman'ish, where we have
>> a parameter exchanged in the initial SSL'ed handshake, which is
>> later used to generate new cancel keys each time the previ
