On Sat, Jul 30, 2005 at 09:35:16PM -0700, Steve Atkins wrote:
> On Sat, Jul 30, 2005 at 11:39:20PM -0400, Bruce Momjian wrote:
> > Let me try to outline where I think our goals are for remote
> > administration. I will not comment on Dave's analysis of the patch
> > review process, but I think he
On Sat, Jul 30, 2005 at 11:39:20PM -0400, Bruce Momjian wrote:
> Let me try to outline where I think our goals are for remote
> administration. I will not comment on Dave's analysis of the patch
> review process, but I think he has some valid points that this patch was
> not treated properly.
>
>
Let me try to outline where I think our goals are for remote
administration. I will not comment on Dave's analysis of the patch
review process, but I think he has some valid points that this patch was
not treated properly.
Basically, I think everyone wants remote administration. Remote
administ
Larry Rosenman wrote:
>
> I think Tom's fix to use IPPROTO_TCP will fix firefly.
>
> LER
And based on the last run, it did.
Thanks, Tom!
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler@lerctr.org
US Mail: 3535 Gaspar Drive
Title: Re: MySQL to PostgreSQL for SugarCRM
Thanks, I'll check it
out. I didn't see much evidence on the SugarCRM site that they are
interested in an DB besides MySQL. But, it is also my hope that the core
SugarCRM project will come around to supporting EDB/PostgreSQL (once we have
done
On Sat, Jul 30, 2005 at 09:47:58AM -0400, Andrew Dunstan wrote:
>
>
> David Fetter wrote:
>
> You have rolled 2 problems into one - spi_query+spi_fetchrow does not
> address the issue of returning large data sets.
>
> Suggest instead:
[suggestion]
Revised patch attached. Thanks for catching
Larry Rosenman wrote:
> I think Tom's fix to use IPPROTO_TCP will fix firefly.
Ah, I forgot about the "we'll just use IP protocol numbers as socket
option levels" behaviour (BSD-derived?). My Linux man page only talks
about SOL_TCP, but I have run into this before and should have
remembered.. my
Andrew Dunstan wrote:
>
> Looks like Unixware is broken too,
>
> cheers
>
> andrew
>
I think Tom's fix to use IPPROTO_TCP will fix firefly.
LER
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler@lerctr.org
US Mail: 3535 Gasp
Bruce Momjian wrote:
Rocco Altier wrote:
This broke the build on AIX.
AIX does not have SOL_TCP as a defined symbol in any of the system
header files.
OK, is there any way of setting the keepalive values on AIX?
Looks like Unixware is broken too,
cheers
andrew
---
Rocco Altier wrote:
> This broke the build on AIX.
>
> AIX does not have SOL_TCP as a defined symbol in any of the system
> header files.
>
OK, is there any way of setting the keepalive values on AIX?
--
Bruce Momjian| http://candle.pha.pa.us
pgman@candle.pha.pa.us
This broke the build on AIX.
AIX does not have SOL_TCP as a defined symbol in any of the system
header files.
-rocco
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Bruce Momjian
> Sent: Saturday, July 30, 2005 11:17 AM
> To: pgsql-comm
> > I'm testing out the latest version of Palles ICU patch on
> win32, and I
> > got the build syste mworking. But it no longer works when
> built - it
> > used to...
> >
> > When initdb:ing with this version and -E UNICODE, I get:
> > WARNING: detected write past chunk end in Analyze Column 0
Michael Glaesemann <[EMAIL PROTECTED]> writes:
> Please find attached diffs for documentation and simple regression
> tests for the new interval->day changes.
The buildfarm results suggest that justify_days is broken in the
integer-datetimes case, eg from panda:
*** ./expected/interval.out
Tom Lane wrote:
> Andrew Dunstan <[EMAIL PROTECTED]> writes:
> > . the thread "windows regression failure - prepared xacts" - in another
> > thread here:
> > http://archives.postgresql.org/pgsql-hackers/2005-07/msg00621.php Tom
> > proposed a possible cause for the problem seen (race conditions
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> . the thread "windows regression failure - prepared xacts" - in another
> thread here:
> http://archives.postgresql.org/pgsql-hackers/2005-07/msg00621.php Tom
> proposed a possible cause for the problem seen (race conditions in
> is_visible() and fri
This has been saved for the 8.2 release:
http://momjian.postgresql.org/cgi-bin/pgpatches_hold
---
Andrew Dunstan wrote:
>
>
> Luke Lonergan wrote:
>
> >Andrew,
> >
> >
> >
> >>Good. So should we roll this up in
Bruce,
some of the items on your patches list don't seem to contain patches ...
In particular,
. the thread "multibyte regression tests" - If you like you can put a
TODO on the list and put my name against it, but I won't be getting to
it any time soon, and nobody else has done any work on
Andrew Dunstan wrote:
>
>
> Bruce,
>
> some of the items on your patches list don't seem to contain patches ...
Right, some are open items, but the patches list is a central place to
put everything.
> In particular,
>
> . the thread "multibyte regression tests" - If you like you can put a
>
David Fetter wrote:
*** 716,724
! In the current implementation, if you are fetching or returning
! very large data sets, you should be aware that these will all go
! into memory.
--- 766,776
! If you are fetch
Seems it's dead on the buildfarm box as well:
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=snake&dt=2005-07-30%20
01:00:01
From what I can tell, the recent patch for O_DIRECT broke it.
//Magnus
---(end of broadcast)---
TIP 2: Don't 'kill -9'
Christopher Kings-Lynne wrote:
They usually claim to be the world's most POPULAR open source database...
Zillions of flies can't be wrong :o)
Regards,
Andreas
---(end of broadcast)---
TIP 6: explain analyze is your friend
They usually claim to be the world's most POPULAR open source database...
Chris
ohp@pyrenet.fr wrote:
Who copied?
I've been to mysql site 2 mn ago (did'nt occur since at least 6 months)
title says : Mysql: The world most advanced opensource database.
Isn't it the title for postgresql?
It see
22 matches
Mail list logo
