I wrote:
> It's usually going to be the case that the oldest datvacuumxid is
> template0's, meaning that it will never be possible to truncate clog
> until autovacuum decides that template0 is at risk of wraparound and
> goes and vacuums it. Shortening the freeze horizon will reduce the size
> tha
"Simon Riggs" <[EMAIL PROTECTED]> writes:
>> On Fri, Nov 03, 2006 at 11:25:09AM -0500, Tom Lane wrote:
>>> Since 8.1 has done this all along and no one's actually complained about
>>> it, I guess no one is using scripts that do "cd". I'm inclined to go
>>> with Bernd's suggestion to change the doc
Tom, Josh, etc.:
> But if you're looking for a "big application" that uses Kerberos,
> there's that pesky thing called Windows. Every single Windows machine in
> an active directory domain environment is a Kerberos client, and uses
> Kerberos for authentication to all network services.
Kerberos w
Life moves on, and I have found it increasingly difficult to maintain
the buildfarm on a day to day basis (not that it needs much, but my
availability is unpredictable). So the good people at CommandPrompt have
responded to my plea for help, and are taking over the management of the
project.
"Sergey E. Koposov" <[EMAIL PROTECTED]> writes:
> So, I send the small doc-patch saying about the space requirement of the
> cluster operation using SELECT ORDER BY.
Added, along with some other minor editorial fixes.
regards, tom lane
---(end of
I am working on the changes necesssary to fix the plperl issue raised a
week or so ago. I have code that can detect if we can safely run two
interpreters. However, things are complicated by the fact that plperl.c
uses a couple of perl hashes to store data: plperl_proc_hash and
plperl_query_h
Josh Berkus writes:
> Yes ... if we were looking to cut down on both code and dependency bugs, we
> might consider desupporting "raw Kerberos". At this point, I think that
> everyone who supports Kerberos supports GSSAPI, unless we're still committed
> to supporting users of Red Hat 7.0 (Tom?
Andrew,
> I am not walking away from the
> project. But this will ensure it gets the TLC it needs and deserves, so
> I am very grateful to Joshua and his team for helping out.
You did a fantastic job putting together the buildfarm, and did more to give
us a regular release cycle than I think an
Tom,
> I have no corporate commitment to make PG 8.3+ work on ancient Red Hat
> versions, if that's what you mean.
Well, in that case my suggestion is that we plan to transition to GSSAPI and
drop support for raw Kerberos as soon as Henry is ready with a patch (plus
I'm going to try to get the
Neil Conway <[EMAIL PROTECTED]> writes:
> I fixed this by adding the appropriate ldap_unbind() calls in error
> control paths. An alternative would be to have a single place do the
> error handling, and jump to that via goto.
Perhaps use a PG_TRY construct?
regards, tom la
Compiled fine. Still a few warnings (using Fedora Core 6 / AMD64).
The new PG_MAGIC_MODULE requirement threw me for a loop. I expect it
will catch others off guard as well.
One of my complicated queries that I threw at it seems to run about
10% - 20% faster now, which is pretty sweet.
The multil
On Sun, Nov 05, 2006 at 01:15:51AM -0500, [EMAIL PROTECTED] wrote:
> One of my complicated queries that I threw at it seems to run about
> 10% - 20% faster now, which is pretty sweet.
I take this back. I forgot to 'analyze'. After 'analyze', the times
returned to the slower 8.1 times. :-(
I will
12 matches
Mail list logo
