Hi all,
I would like to submit two ideas:
1/
In the daily tasks I have as (also) a standard DBA, I found usefull to
view locks in a human point of view. I think the ~ '^pg_' part of the
queries may be not so clean... Any ideas welcome :)
2/
Also, I like having a cache hit/miss ratio. This is
Hi, Hannu,
Hannu Krosing wrote:
Are you sure it's UCS-4 ? I've always thought that XML is what is given
in xml tag, and utf-8 if no charset is given.
You have to distinguish between the supported charset, and the document
encoding.
UCS-4 and UTF-8 are both encodings for UNICODE
see:
Hi, Bruce,
Bruce Momjian wrote:
I don't think that any of our SGML documentation is actually in UCS-4
encoding.
The source files use nothing beyond plain ASCII (and should remain that
way, IMHO) so there isn't any need to inquire very far into exactly what
the toolchain thinks the document
Am Montag, 25. September 2006 04:04 schrieb ITAGAKI Takahiro:
#shared_buffers = 32000kB # min 128kB or max_connections*16kB
#temp_buffers = 8000kB # min 800kB
#effective_cache_size = 8000kB
Are there any reasons to continue to use 1000-unit numbers? Megabyte-unit
(32MB and
current default of 1000 pages (8Mb) seems really pretty silly for modern
machines; we could certainly set it to 10 times that without problems,
and maybe much more. Thoughts?
May be, set by default effective_cache_size equal to number of shared buffers?
If pgsql is configured to use quarter
Hello,
The Cassowary buildfarm memeber is curently failing when performing initdb .
The corresponding log file initdb.log is empty.
When running initdb manually, it dies immediately with code 0200.
Other executables (psql, createlang, createdb for example) fail in the same
manner. But some
On Fri, 2006-09-22 at 14:16 +0100, Dave Page wrote:
Following the recent discussion on this list and another on pgsql-core,
we have decided that we would like to aim to meet the following schedule
for the release of PostgreSQL 8.3:
April 1st 2007 - Feature freeze
May 1st 2007 - Beta 1
Hi,
I just read the docs about DELETE RETURNING in 8.2, and a small idea arised:
INSERT INTO logtable DELETE * FROM lifetable WHERE date'2006-01-01'
RETURNING *;
Will this work as expected?
It might be a good example to put into the docs then.
If not, it may be worth the effort to make it
On Sun, Sep 24, 2006 at 08:54:35PM +0100, Dave Page wrote:
Snake and Bandicoot are still hanging in ECPG-Check at the moment.
Killing the dt_test.exe program that the regression tests seem to be
running frees it all up to properly report the failure. I don't have
time to investigate further at
-Original Message-
From: Michael Meskes [mailto:[EMAIL PROTECTED]
Sent: 25 September 2006 11:57
To: Dave Page
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Windows build farm failures
On Sun, Sep 24, 2006 at 08:54:35PM +0100, Dave Page wrote:
Snake and Bandicoot
At the end of the following page:http://www.postgresql.org/docs/8.0/static/indexes-partial.htmlthere is a link [
Generalized Partial Indexes] which is pointing to a missing link. Can someone update the link with a live doc? Probably
this one Regards,-- [EMAIL PROTECTED][EMAIL PROTECTED] gmail |
Hi,
http://developer.postgresql.org/pgdocs/postgres/release-8-2.html tells:
Add pg_dump -X no-data-for-failed-tables option to suppress loading
data if table creation failed (the table already exists) (Martin
Pitt)
However, http://developer.postgresql.org/pgdocs/postgres/app-pgdump.html
seem
On Sep 22, 2006, at 2:50 PM, Joshua D. Drake wrote:
And how were you planning to tell if a patch cam from a regular?
Hopefully
you weren't planning on blindly trusting the from header.
Misuse of the build farm in a way the effects other sites could
get the
project a big black eye, so you
I just had a look at the reports and it seems we have several
things going on:
1) libpq gives additional information when not able to connect:
could not connect to server: Connection refused
(0x274D/10061)
instead of just:
could not connect to server: Connection refused
On 25-Sep-06, at 4:31 AM, Markus Schaber wrote:
Hi,
I just read the docs about DELETE RETURNING in 8.2, and a small
idea arised:
INSERT INTO logtable DELETE * FROM lifetable WHERE date'2006-01-01'
RETURNING *;
Will this work as expected?
What is your expected result here ? It would
It's very weird, because if you get through to this stage it means you
have already run initdb successfully during the make-check stage.
Certainly the trace below looks like it's a failure in the startup code
- maybe a DLL mismatch, although that shouldn't be possible? Does your
Cygwin
Teodor Sigaev wrote:
current default of 1000 pages (8Mb) seems really pretty silly for modern
machines; we could certainly set it to 10 times that without problems,
and maybe much more. Thoughts?
May be, set by default effective_cache_size equal to number of shared
buffers?
If pgsql is
On Sun, Sep 24, 2006 at 11:51:49AM +0100, Dave Page wrote:
wrong to the monitoring processes - what had happened was that both had
hung or got in an inifinite loop in ECPG-check, the machine was running
just fine
Is this still an issue? Can you provide more information? What happens if you
run
Hi, Dave,
Dave Cramer wrote:
I just read the docs about DELETE RETURNING in 8.2, and a small idea
arised:
INSERT INTO logtable DELETE * FROM lifetable WHERE date'2006-01-01'
RETURNING *;
Will this work as expected?
What is your expected result here ? It would return all the rows that
Linux:
$ echo 'DROP FUNCTION if exists foo(int);' | psql 1c
Timing is on.
SET
Time: 197.941 ms
NOTICE: function foo(░) does not exist ... skipping
ERROR: invalid byte sequence for encoding UTF8: 0x90
HINT: This error can also happen if the byte sequence does not match the
encoding expected
Linux:
$ echo 'DROP FUNCTION if exists foo(int);' | psql 1c Timing is on.
SET
Time: 197.941 ms
NOTICE: function foo(░) does not exist ... skipping
ERROR: invalid byte sequence for encoding UTF8: 0x90
HINT: This error can also happen if the byte sequence does not
match the encoding
Not being an expert, but to me it looks like the client_encoding being set to
UTF8 but the data being sent is something other than UTF8. I've seen this
happen on Linux when connecting with PuTTY from Windows (and then psql from
the linux machine) and having the wrong encoding set in PuTTY.
Hi, Csaba,
Csaba Nagy wrote:
dbval=# select 1;
ERROR: column 1 does not exist
The full story is that I typed 'ü' (u-umlaut if it won't render
correctly) and backspace before the '1'. I guess the backspace will
delete byte-wise and will so fail to delete properly multi-byte
characters.
Not being an expert, but to me it looks like the client_encoding being set to
UTF8 but the data being sent is something other than UTF8. I've seen this
happen on Linux when connecting with PuTTY from Windows (and then psql from the
linux machine) and having the wrong encoding set in PuTTY. I'd
-Original Message-
From: Joachim Wieland [mailto:[EMAIL PROTECTED]
Sent: 25 September 2006 13:25
To: Dave Page
Cc: Andrew Dunstan; pgsql-hackers@postgresql.org;
[EMAIL PROTECTED]
Subject: Re: [HACKERS] Buildfarm alarms
On Sun, Sep 24, 2006 at 11:51:49AM +0100, Dave Page
postgres=# drop type if exists foo;
NOTICE: type foo does not exist, skipping
DROP TYPE
postgres=# drop table if exists foo;
NOTICE: table foo does not exist, skipping
DROP TABLE
postgres=# drop function if exists foo();
NOTICE: function foo() does not exist ... skipping
DROP FUNCTION
Jeremy Drake [EMAIL PROTECTED] writes:
I just tried using the \lo_import command in a regression test, and I
think I figured out why this will not work:
...
Yes, that's the large object OID in the output there, and it is different
each run (as I expect).
Right. I'd suggest temporarily
On Fri, Sep 22, 2006 at 12:59:36PM -0700, Joe Conway wrote:
Andrew Sullivan wrote:
On Thu, Sep 21, 2006 at 03:05:36PM -0500, Jim C. Nasby wrote:
Regardless, I think we should include a section of major new
projects/developments from pgFoundry, because they ultimately make
PostgreSQL a more
Teodor Sigaev wrote:
postgres=# drop type if exists foo;
NOTICE: type foo does not exist, skipping
DROP TYPE
postgres=# drop table if exists foo;
NOTICE: table foo does not exist, skipping
DROP TABLE
postgres=# drop function if exists foo();
NOTICE: function foo() does not exist ... skipping
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jim C. Nasby
Sent: 25 September 2006 15:03
To: Joe Conway
Cc: Andrew Sullivan; pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Release Notes: Major Changes in 8.2
For
example, didn't
Andrew Dunstan [EMAIL PROTECTED] writes:
Yes, this appears to be a bug, not related to encoding etc. Maybe we
should be calling func_signature_string in generating this error.
Can't, because you don't have an Oid array for the types.
TypeNameToString is the correct thing --- I'm considering
On Sun, Sep 24, 2006 at 12:26:55AM -0400, Alvaro Herrera wrote:
Joshua D. Drake wrote:
Tom Lane wrote:
I asked around inside Red Hat but haven't gotten any responses yet ...
seeing that it's a rather old Suse kernel, I can understand that RH's
kernel hackers might not be too excited
Found a problem:
ereport(NOTICE,
(errmsg(function %s(%s) does not exist ... skipping,
NameListToString(functionName),
NameListToString(argTypes;
NameListToString() suppose as an argument List of Value nodes, but
argTypes is a
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
Yes, this appears to be a bug, not related to encoding etc. Maybe we
should be calling func_signature_string in generating this error.
Can't, because you don't have an Oid array for the types.
TypeNameToString is the correct
Markus Schaber [EMAIL PROTECTED] writes:
http://developer.postgresql.org/pgdocs/postgres/release-8-2.html tells:
Add pg_dump -X no-data-for-failed-tables option to suppress loading
data if table creation failed (the table already exists) (Martin
Pitt)
However,
On Mon, Sep 25, 2006 at 03:10:39PM +0100, Dave Page wrote:
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jim C. Nasby
For example, didn't pgAdmin just add support for Slony? That's
something worth mentioning.
That was our last major release. You can see what will be
-Original Message-
From: David Fetter [mailto:[EMAIL PROTECTED]
Sent: 25 September 2006 16:57
To: Dave Page
Cc: Jim C. Nasby; Joe Conway; Andrew Sullivan;
pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Release Notes: Major Changes in 8.2
On Mon, Sep 25, 2006 at
Folks,
On Thu, Sep 21, 2006 at 03:05:36PM -0500, Jim C. Nasby wrote:
Regardless, I think we should include a section of major new
projects/developments from pgFoundry, because they ultimately make
PostgreSQL a more useful database. Maybe this list should only be in the
I like that. New
[RESENT in a modified version since the original reply seems to have ben
lost by the listserver which seems to happen sometimes lately]
Tom Lane wrote:
Matteo Beccati [EMAIL PROTECTED] writes:
Tom Lane ha scritto:
Matteo Beccati [EMAIL PROTECTED] writes:
I cannot see anything bad by using
Andrew Dunstan [EMAIL PROTECTED] writes:
Initdb does not currently make any attempt to discover the extent of
physical or virtual memory, it simply tries to start postgres with
certain shared_buffer settings, starting at 4000, and going down until
we get a success.
max_fsm_pages is now
On Fri, Sep 22, 2006 at 12:59:36PM -0700, Joe Conway wrote:
In that case, what about things on gborg too?
Yes, same idea. I don't care where the project _lives_; the
important thing is its integration with PostgreSQL (and its quality).
A
--
Andrew Sullivan | [EMAIL PROTECTED]
When my
Hi Mark,
Thanks for doing the test. I checked out the link you provided below. I am a
little confused about the goal of these tests. Do you plan to test the
overall performance of postgreSQL on handling TPC-H queries?
Thanks,
Jie
On 9/22/06 3:45 PM, Mark Wong [EMAIL PROTECTED] wrote:
Jie
Hi Jie,
Yeah, basically gather as many stats as I can to accurately profile the
overall system performance. I thought it would be appropriate to use a
TPC-H based workload as one measuring stick to use for bitmap indexes.
Mark
Jie Zhang wrote:
Hi Mark,
Thanks for doing the test. I
On Mon, Sep 25, 2006 at 10:03:50AM +0200, Peter Eisentraut wrote:
Am Montag, 25. September 2006 04:04 schrieb ITAGAKI Takahiro:
#shared_buffers = 32000kB # min 128kB or max_connections*16kB
#temp_buffers = 8000kB # min 800kB
#effective_cache_size = 8000kB
Are there any
On Mon, 2006-09-25 at 16:44 +0530, Gurjeet Singh wrote:
At the end of the following page:
http://www.postgresql.org/docs/8.0/static/indexes-partial.html
there is a link [Generalized Partial Indexes] which is pointing to a
missing link.
I agree the link should be fixed, but I can't see
On Mon, Sep 25, 2006 at 09:29:28AM +0200, Jean-Paul Argudo wrote:
Hi all,
I would like to submit two ideas:
1/
In the daily tasks I have as (also) a standard DBA, I found usefull to
view locks in a human point of view. I think the ~ '^pg_' part of the
queries may be not so clean... Any
I'm playing with catalog upgrade via BKI format. I enhanced the pg_dump
of BKI output (not patch ready yet). I'm using it for some test now, but
I think It should be useful for some one other, for example some
application with embedded postgres should use own prepared BKI for
database init
Zdenek Kotala [EMAIL PROTECTED] writes:
I'm playing with catalog upgrade via BKI format. I enhanced the pg_dump
of BKI output (not patch ready yet). I'm using it for some test now, but
I think It should be useful for some one other, for example some
application with embedded postgres should
Zdenek Kotala wrote:
I'm playing with catalog upgrade via BKI format. I enhanced the
pg_dump of BKI output (not patch ready yet). I'm using it for some
test now, but I think It should be useful for some one other, for
example some application with embedded postgres should use own
prepared BKI
Mark,
On 9/25/06 11:32 AM, Mark Wong [EMAIL PROTECTED] wrote:
Yeah, basically gather as many stats as I can to accurately profile the
overall system performance. I thought it would be appropriate to use a
TPC-H based workload as one measuring stick to use for bitmap indexes.
Note that the
Tom Lane wrote:
Zdenek Kotala [EMAIL PROTECTED] writes:
I'm playing with catalog upgrade via BKI format. I enhanced the pg_dump
of BKI output (not patch ready yet). I'm using it for some test now, but
I think It should be useful for some one other, for example some
application with embedded
All,
Here:
http://pgfoundry.org/docman/view.php/147/233/release82.zip
is a zip file of a draft of the PostgreSQL 8.2 release and accompanying
press kit. Please check if the technical details are correct, and get
back to me with any corrections by Thursday.
Thanks!
--
--Josh
Josh Berkus
Josh Berkus josh@agliodbs.com writes:
http://pgfoundry.org/docman/view.php/147/233/release82.zip
is a zip file of a draft of the PostgreSQL 8.2 release and accompanying
press kit. Please check if the technical details are correct, and get
back to me with any corrections by Thursday.
Stefan Kaltenbrunner [EMAIL PROTECTED] writes:
http://www.kaltenbrunner.cc/files/analyze_q9_beta1.txt
The next problem seems to be the drastic misestimation of this join
size:
- Nested Loop (cost=0.00..6872092.36 rows=135 width=28) (actual
time=94.762..14429291.129 rows=3554044 loops=1)
Tom,
Thursday? My, we're feeling optimistic about the length of the beta
period, aren't we?
It takes me a minumum of 2 weeks (preferably 3) to deal with the
translations. If we stay on schedule, I'll be *just* ready for a 1-month
beta.
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San
Neil Conway [EMAIL PROTECTED] writes:
I agree the link should be fixed, but I can't see another canonical
location for the document online: linking to CiteSeer (which itself is
generated from the mention in our online docs) is probably not wise.
citeseer's cache still has the paper, and in it
Michael Meskes [EMAIL PROTECTED] writes:
This double stuff creates so many headaches that I wonder if we
better not test it at all in the regression suite. Comments?
If you're not prepared to support alternative expected files (as the
main regression tests do), then I think you have
Jim C. Nasby wrote:
The reason with the shared_buffers is that the detection code in
initdb has 400kB as minimum value, and it would be pretty
complicated to code the detection code to handle both kB and MB
units. If someone wants to try it, though, please go ahead.
What about 0.4MB?
On Sep 25, 2006, at 1:03 AM, Peter Eisentraut wrote:
Am Montag, 25. September 2006 04:04 schrieb ITAGAKI Takahiro:
#shared_buffers = 32000kB # min 128kB or max_connections*16kB
#temp_buffers = 8000kB # min 800kB
#effective_cache_size = 8000kB
Are there any reasons to continue
Peter Eisentraut [EMAIL PROTECTED] wrote:
#max_fsm_pages = 160# min max_fsm_relations*16, 6 bytes each
max_fsm_pages doesn't have a discernible unit
Yes, max_fsm_*pages* doesn't have a unit, but can we treat the value as
the amount of trackable database size by fsm or estimated
60 matches
Mail list logo
