Please see the attached file for details.
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
See the attached file for details
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
Guys,
So ... do we have full IPv6 support in 7.4, or what?
--
Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHe
On Wed, Aug 20, 2003 at 08:22:51AM -0700, Josh Berkus wrote:
> Guys,
>
> So ... do we have full IPv6 support in 7.4, or what?
For the network ipv6 support: It should all work.
Afaik, there is only 1 piece of the networking code left that
doesn't support ipv6 and that is Kerberos 4. And that is
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> Why not wrap all 'identifier' outputs in a call to the quoting function, so
> the above message would in fact appear as:
> table schema.foo does not exist
> but with a space in it it would appear like this:
> table "schema 2".foo does not exis
On Fri, 8 Aug 2003 16:53:48 -0700, Sean Chittenden
<[EMAIL PROTECTED]> wrote:
>the problem with your patch was
>that it picked an index less often than the current code when there
>was low correlation.
Maybe bit rot? What version did you apply the patch against? Here is
a new version for Postgre
Hackers,
I've been searching the archives, but I can't find the thread from last month
where we discussed the problem with Linux memory overcommits in kernel 2.4.x.
Can someone point me to the right thread? I think maybe the subject line was
something deceptive
--
-Josh Berkus
Aglio D
http://archives.postgresql.org/pgsql-hackers/2003-07/msg00608.php
Subject is "reprise on Linux overcommit handling" - is that too
deceptive? :-)
andrew
Josh Berkus wrote:
Hackers,
I've been searching the archives, but I can't find the thread from last month
where we discussed the problem wi
Josh Berkus <[EMAIL PROTECTED]> writes:
> Do we have full Rendezvous and IPv6 support in 7.4? That is, sufficient to
> shout about in our PR materials?
The IPv6 support does everything you could want AFAIK, and is certainly
worth a bullet point.
I'm not sure how "full" the Rendezvous support is
On 8/20/2003 1:02 PM, Josh Berkus wrote:
>Hackers,
>
>I've been searching the archives, but I can't find the thread from last month
>where we discussed the problem with Linux memory overcommits in kernel 2.4.x.
>
>Can someone point me to the right thread? I think maybe the subject line was
>so
Koichi Suzuki <[EMAIL PROTECTED]> writes:
> I need to know where such "lock marks" are stored in the source level.
A row lock is represented by storing the locking transaction's ID in
xmax and setting the HEAP_MARKED_FOR_UPDATE infomask bit. The bit is
needed to distinguish this from the case whe
Recent discussion of index cost estimation ("[HACKERS] Correlation in
cost_index()" ca. two weeks ago) has lead to the conclusion that the
column correlation calculated by VACUUM does not always help when we
want to find out how well index access order corresponds to physical
tuple position. Most
hi
im having a problem while using the PQcmdTuples(). Consider the following
code snippet:
there exists a table table1 (name character(30), age integer)
<...snip...>
PGresult *res = PQexec("prepare p_stmt (integer) update table1 set age = age
+ 1 where age = $1");
PQclear (res);
res = PQexec ( ex
Antigen for Exchange found application.pif matching FILE FILTER= *.* file
filter.
The file is currently Removed. The message, "Re: Details", was
sent from [EMAIL PROTECTED] and was discovered in IMC
Queues\Inbound
located at Royal Group Technologies Limited/Royalgroup/MAILDEPOT.
PRIVILEGED / CON
14 matches
Mail list logo
