Luke Lonergan wrote:
Stefan,
On 3/10/06 12:23 PM, Stefan Kaltenbrunner [EMAIL PROTECTED] wrote:
wrong(or rather extremely optimistic) the array itself only has two
(redundant) FC-loops(@2GB )to the attached expansion chassis. The array
has 2 active/active controllers (with a failover
Stefan,
On 3/11/06 12:21 AM, Stefan Kaltenbrunner [EMAIL PROTECTED] wrote:
So - you're getting 20MB/s on loading from a potential of 200MB/s?
no - I can write 110MB/s on thw WAL LUN and 110MB/s on the other LUN
concurrently.
The numbers you published earlier show you are getting a maximum
Tom Lane wrote:
Stefan Kaltenbrunner [EMAIL PROTECTED] writes:
3. vacuuming this table - it turned out that VACUUM FULL is completly
unusable on a table(which i actually expected before) of this size not
only to the locking involved but rather due to a gigantic memory
requirement and
i am trying to download the windows version since 3 hours
ago and just
get an error page no matters if i try the FTP browser, ftp
mirrors or
bittorrent
Fixed now, thanks for reporting.
//Magnus
---(end of broadcast)---
TIP 2: Don't
Hi,
this is from HEAD of a few days ago, it looks suspicious to me.
8.2devel runs on port 5433.
[EMAIL PROTECTED]:~/pgsql$ bin/psql -p 5433 template1 markus
Welcome to psql 8.2devel, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help with SQL
On Mar 11, 2006, at 19:13 , Markus Bertheau wrote:
Why is it trying to use 5432? Am I missing something? Is that the
expected behaviour?
Was your 8.2devel install built with the default port of 5432? (i.e.,
do you need to set the port to 5433 in postgresql.conf or at server
start? It
On Mar 11, 2006, at 19:36 , Markus Bertheau wrote:
I'm pretty sure you didn't have to specify the port with \c again in
earlier versions - so this is a regression, and a confusing one imho
You couldn't connect to another host from the same psql session, so
including the port wasn't even an
On Saturday 11 March 2006 05:51, Michael Glaesemann wrote:
On Mar 11, 2006, at 19:36 , Markus Bertheau wrote:
I'm pretty sure you didn't have to specify the port with \c again in
earlier versions - so this is a regression, and a confusing one imho
You couldn't connect to another host from
In an attempt to throw the authorities off his trail, pgman@candle.pha.pa.us
(Bruce Momjian) transmitted:
Jan Wieck wrote:
We've been there before, and not only once. I wonder why we still find
more of these, because every time it comes up I agree to removal of it.
Perhaps your name
Quoth [EMAIL PROTECTED] (Marc G. Fournier):
Just curious, but how do ppl come to Canada as tourists from other
countries? I don't imagine they need to be invited by a Canadian,
do they?
Well, the invitation thing doesn't apply at all to people from North
America or Western Europe; it's
It's still not easy to come from Russia to Canada. I have to convince
officer in canadian embassy that
1) I have enough money for living in Canada
2) I don't want to immigrate
3) I'm a loyal citizen
Invitation from conference commitee could help me to get an official letter
from my institute to
Neil Conway wrote:
On Thu, 2006-03-09 at 17:29 -0400, Bruce Momjian wrote:
Remove Jan Wieck's name from copyrights, and put in standard
boilerplate, with approval of author.
You missed a few:
src/pl/tcl/pltcl.c
src/pl/tcl/license.terms
src/backend/utils/adt/ruleutils.c
I'd fix
Markus Bertheau [EMAIL PROTECTED] writes:
Why is it trying to use 5432? Am I missing something? Is that the
expected behaviour?
Michael Fuhr hinted that
http://archives.postgresql.org/pgsql-committers/2006-02/msg00139.php
may be the cause of that.
Confirmed here: \c drops the previous port
On 3/10/06, Pavel Stehule [EMAIL PROTECTED] wrote:
Hello,
I want do sql wrap for woid plpgsql function. But void SQL function must not
finish SELECT cmd. I don't know any others command which I can use.
Can You help me?
Thank You
Pavel Stehule
perform * from your_table;
--
Atentamente,
Tom Lane wrote:
I wrote:
Stefan Kaltenbrunner [EMAIL PROTECTED] writes:
samples %symbol name
350318533 98.8618 mergepreread
9718220.2743 tuplesort_gettuple_common
4136740.1167 tuplesort_heap_siftup
I don't have enough memory to really reproduce this, but I've come close
From: Jaime Casanova [EMAIL PROTECTED]
To: Pavel Stehule [EMAIL PROTECTED]
CC: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Function's final statement must not be a SELECT
Date: Sat, 11 Mar 2006 12:42:15 -0500
On 3/10/06, Pavel Stehule [EMAIL PROTECTED] wrote:
Hello,
I want do sql
Ühel kenal päeval, R, 2006-03-10 kell 12:23, kirjutas Steve Atkins:
I get bitten by this quite often (customer machines, one giant table,
purge out a lot of old data).
CLUSTER is great for that, given the headroom, though I've often
resorted to a dump and restore because I've not had the
Hannu Krosing [EMAIL PROTECTED] writes:
At some point I had to compress a very busily updated table. I used the
following approach:
[ move a few rows at a time ]
We could possibly do something similar with VACUUM FULL as well: once
maintenance_work_mem is filled, start discarding per-page data
Mark,
I have tried your patches and it worked great. Thanks.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
Tom Lane wrote:
Mark Kirkwood [EMAIL PROTECTED] writes:
Good points! I had not noticed this test case. Probably NULL is better
Would setting it to 'BLCKSZ - (fixed index header stuff)'
BTW, I noticed difference of outputs from pg_freespacemap and
pgstattuple.
I ran pgbench and inspected accounts table by using these tools.
pg_freespacemap:
sum of bytes: 250712
pgstattuple:
free_space: 354880
Shouldn't they be identical?
--
Tatsuo Ishii
SRA OSS, Inc. Japan
On Sat, Mar 11, 2006 at 12:15:08PM -0500, Tom Lane wrote:
Markus Bertheau [EMAIL PROTECTED] writes:
Why is it trying to use 5432? Am I missing something? Is that the
expected behaviour?
Michael Fuhr hinted that
http://archives.postgresql.org/pgsql-committers/2006-02/msg00139.php
may
I'm now participating in a PG project.I need to modify some parts of the
log buffer flushing function and the data buffer flushing function.I don't
know where they are.
Could you tell me where the following two functions are:
--Log Buffer Flush:Only flush the dirty log buffer into the
22 matches
Mail list logo
