Am Sonntag, 24. Juli 2005 17:53 schrieb Tom Lane:
I'm wondering why we still have a README there at all --- it's entirely
superseded by the SGML documentation.
http://developer.postgresql.org/docs/postgres/regress-evaluation.html
I think we kept it there so people can read it during the
Peter Eisentraut [EMAIL PROTECTED] writes:
Am Sonntag, 24. Juli 2005 17:53 schrieb Tom Lane:
I'm wondering why we still have a README there at all --- it's entirely
superseded by the SGML documentation.
http://developer.postgresql.org/docs/postgres/regress-evaluation.html
I think we kept
Patch applied. Thanks. /contrib/dbsize removed. New functions:
pg_tablespace_size
pg_database_size
pg_relation_size
pg_complete_relation_size
pg_size_pretty
---
Dave Page wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dave Page
Sent: 28 July 2005 16:16
To: Bruce Momjian; Tom Lane
Cc: PostgreSQL-development
Subject: Re: [HACKERS] --enable-thread-safety on Win32
OK, but I would then like someone to actually
Dave Page dpage@vale-housing.co.uk writes:
However In all but one place in libpq, we don't use errno anyway
(actually 2, but one is a bug anyway) because we use GetLastError()
instead (which tested thread safe as well FWIW). The only place it's
used is PQoidValue():
result =
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 seems weird for both projects to have the same claim (although it's
true for postgreql...)
Regards
--
OHP,
title says : Mysql: The world most advanced opensource database.
Just to head this off: no, it doesn't.
It says: MySQL: The world's most popular open source database
^
That's been their slogan for quite a while. It's not precisely
On Friday 29 July 2005 10:33, 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.
I just checked and it states (exactly what it has for years)
The world's most popular open
On Thu, Jul 28, 2005 at 05:00:44PM -0700, Mark Wong wrote:
On Thu, 28 Jul 2005 16:55:55 -0700
Mark Wong [EMAIL PROTECTED] wrote:
On Thu, 28 Jul 2005 18:48:09 -0500
Jim C. Nasby [EMAIL PROTECTED] wrote:
On Thu, Jul 28, 2005 at 04:15:31PM -0700, Mark Wong wrote:
On Thu, 28 Jul 2005
On Fri, 29 Jul 2005 14:39:08 -0500
Jim C. Nasby [EMAIL PROTECTED] wrote:
On Thu, Jul 28, 2005 at 05:00:44PM -0700, Mark Wong wrote:
On Thu, 28 Jul 2005 16:55:55 -0700
Mark Wong [EMAIL PROTECTED] wrote:
On Thu, 28 Jul 2005 18:48:09 -0500
Jim C. Nasby [EMAIL PROTECTED] wrote:
On Fri, Jul 29, 2005 at 12:51:57PM -0700, Mark Wong wrote:
Not sure I fully understand what you're trying to say, but it seems like
it might still be worth trying my original idea of just turning all 80
disks into one giant RAID0/striped array and see how much more bandwidth
you get out of
On Fri, 29 Jul 2005 14:57:42 -0500
Jim C. Nasby [EMAIL PROTECTED] wrote:
On Fri, Jul 29, 2005 at 12:51:57PM -0700, Mark Wong wrote:
Not sure I fully understand what you're trying to say, but it seems like
it might still be worth trying my original idea of just turning all 80
disks into
Mark,
I have done that before actually, when the tablespace patch came out. I
was able to get almost 40% more throughput with half the drives than
striping all the disks together.
That's not the figures you showed me. In your report last year it was 14%,
not 40%.
--
Josh Berkus
Aglio
On Fri, 29 Jul 2005 13:35:32 -0700
Josh Berkus josh@agliodbs.com wrote:
Mark,
I have done that before actually, when the tablespace patch came out. I
was able to get almost 40% more throughput with half the drives than
striping all the disks together.
That's not the figures you
On Fri, 29 Jul 2005 13:19:06 -0700
Luke Lonergan [EMAIL PROTECTED] wrote:
Mark,
On 7/29/05 12:51 PM, Mark Wong [EMAIL PROTECTED] wrote:
Adaptec 2200s
Have you tried non-RAID SCSI controllers in this configuration? When we
used the Adaptec 2120s previously, we got very poor
Josh Berkus wrote:
OHP,
title says : Mysql: The world most advanced opensource database.
Just to head this off: no, it doesn't.
It says: MySQL: The world's most popular open source database
^
That's been their slogan for quite
Bruce Momjian wrote:
Josh Berkus wrote:
OHP,
title says : Mysql: The world most advanced opensource database.
Just to head this off: no, it doesn't.
It says: MySQL: The world's most popular open source database
^
On Fri, Jul 29, 2005 at 01:11:35PM -0700, Mark Wong wrote:
On Fri, 29 Jul 2005 14:57:42 -0500
Jim C. Nasby [EMAIL PROTECTED] wrote:
On Fri, Jul 29, 2005 at 12:51:57PM -0700, Mark Wong wrote:
Not sure I fully understand what you're trying to say, but it seems like
it might still be
On Tue, Jul 26, 2005 at 10:17:05PM +0200, Palle Girgensohn wrote:
--On tisdag, juli 26, 2005 15.17.57 -0400 Tom Lane [EMAIL PROTECTED]
wrote:
Larry Rosenman ler@lerctr.org writes:
On Jul 26 2005, Jim C. Nasby wrote:
So the question now is: how do we fix the issue with threaded python?
Jim C. Nasby wrote:
My buildfarm machine
(http://pgbuildfarm.org/cgi-bin/show_history.pl?nm=octopusbr=HEAD)
is SMP, so if anything we need UP testing.
My UP 4.11-STABLE box is back accessable again.
If someone wants, I can set up another buildfarm member...
LER
--
Larry Rosenman
Christopher Kings-Lynne wrote:
How about a PQescapeIdentifier function in libpq? :)
Good idea, added to TODO.
--
Bruce Momjian| http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
Stephen Frost wrote:
-- Start of PGP signed section.
* Jim C. Nasby ([EMAIL PROTECTED]) wrote:
On Thu, Jul 07, 2005 at 01:48:59PM -0400, Tom Lane wrote:
I don't really agree with the viewpoint that truncate is just a quick
DELETE, and so I do not agree that DELETE permissions should be
Added to TODO:
* Add system view to show free space map contents
---
Simon Riggs wrote:
On Tue, 2005-07-12 at 14:56 -0700, Joshua D. Drake wrote:
It'd be relatively easy I think to extract the current FSM
Would someone who knows perl update plperl.sgml and send me a patch?
Also, is this still true in 8.1:
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.
Added to TODO:
* Prevent inherited tables from expanding temporary subtables of other
sessions
---
Thomas F. O'Connell wrote:
On Jul 21, 2005, at 1:22 PM, Bruce Momjian wrote:
Thomas F. O'Connell
Simon Riggs wrote:
On Sun, 2005-07-24 at 17:57 +0900, Tatsuo Ishii wrote:
It seems current CE implementation ignores UPDATE, DELETE quries. Is
this an intended limitation?
Yes, it does not currently optimise the execution of UPDATE/DELETE
against a parent table.
This is not an intended
Alvaro Herrera wrote:
On Thu, Jul 28, 2005 at 01:59:10PM -0400, Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
I just noticed the createuser and dropuser pages may need
adjustments as well ... are you still working on this?
The programs themselves need adjustment, too :-(.
I have just loaded the patches list with all outstanding patches that
need consideration, and updated the open items list:
http://momjian.postgresql.org/cgi-bin/pgpatches
http://momjian.postgresql.org/cgi-bin/pgopenitems
We will need to make some decisions on that goes into 8.1.
On Fri, Jul 29, 2005 at 11:24:37PM -0400, Bruce Momjian wrote:
Would someone who knows perl update plperl.sgml and send me a patch?
Also, is this still true in 8.1:
In the current implementation, if you are fetching or returning
very large data sets, you should be aware that
29 matches
Mail list logo