Hi all,
As AUTOVACUUM is having multiple workers now, the semantics of
autovacuum_cost_limit also need to be redefined.
Currently, autovacuum_cost_limit is the accumulated cost that will cause
one single worker vacuuming process to sleep. It is used to restrict
the I/O consumption of a single
Zoltan Boszormenyi írta:
Zdenek Kotala írta:
Zoltan Boszormenyi wrote:
Hi,
we have found that psql in PostgreSQL 8.2.3
has problems connecting to the server
running on Solaris 10/Sun SPARC.
$ uname -a
SunOS dev-machine 5.10 Generic_118833-36 sun4u sparc SUNW,Sun-Fire-V440
It seems that
Zoltan Boszormenyi írta:
Zoltan Boszormenyi írta:
Zdenek Kotala írta:
Zoltan Boszormenyi wrote:
Hi,
we have found that psql in PostgreSQL 8.2.3
has problems connecting to the server
running on Solaris 10/Sun SPARC.
$ uname -a
SunOS dev-machine 5.10 Generic_118833-36 sun4u sparc
ITAGAKI Takahiro [EMAIL PROTECTED] writes:
Tom Lane [EMAIL PROTECTED] wrote:
Backend encodings must have the property
that all bytes of a multibyte character are = 128.
But then, PG_JOHAB have already infringed it. Please see johab_to_utf8.map.
Trailing bytes of JOHAB can be less than
FWIW, it looks like it failed to reject stopwords. Is it possible you
Right.
I suppose the problem is with '\r\n'... Try attached patch.
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
WWW: http://www.sigaev.ru/
ITAGAKI Takahiro [EMAIL PROTECTED] writes:
Tom Lane [EMAIL PROTECTED] wrote:
Backend encodings must have the property
that all bytes of a multibyte character are = 128.
But then, PG_JOHAB have already infringed it. Please see johab_to_utf8.map.
Trailing bytes of JOHAB can be less than
It's been known for years that commit_delay isn't very good at giving us
group commit behavior. I did some experiments with this simple test
case: BEGIN; INSERT INTO test VALUES (1); COMMIT;, with different
numbers of concurrent clients and with and without commit_delay.
Summary for the
On Mon, Mar 26, 2007 at 02:32:26PM +0400, Teodor Sigaev wrote:
FWIW, it looks like it failed to reject stopwords. Is it possible you
Right.
I suppose the problem is with '\r\n'... Try attached patch.
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
Yup, that solved the problem, thanks.
I'll commit extended patch - there is one more place with the same bug.
Wouldn't it be more efficiently written to walk the string backwards until
!isspace instead? Not sure that it matters at all, but then you'll
normallyi never step over more than two
Yup, that solved the problem, thanks. I'll commit extended patch - there
is one more place with the same bug.
Ok, thanks.
Wouldn't it be more efficiently written to walk the string backwards until
!isspace instead? Not sure that it matters at all, but then you'll
normallyi never step
Hello,
I propose integration plpgpsm into core PostgreSQL.
plpgpsm is SQL/PSM language implementation for PostgreSQL based on pl/pgsql
runtime. Currently this modified runtime exists for PostgreSQL 8.1, 8.2 and
CVS HEAD.
Some information:
* http://pgfoundry.org/projects/plpsm/
*
Teodor Sigaev [EMAIL PROTECTED] writes:
! pbuf = buf;
! while( !isspace( *pbuf ) )
! pbuf++;
! *pbuf = '\0';
Surely the loop needs to look like
while (*pbuf !isspace(*pbuf))
Tom Lane wrote:
Teodor Sigaev [EMAIL PROTECTED] writes:
! pbuf = buf;
! while( !isspace( *pbuf ) )
! pbuf++;
! *pbuf = '\0';
Surely the loop needs to look like
while (*pbuf
Tatsuo Ishii [EMAIL PROTECTED] writes:
Sigh. From the first day when JOHAB was supported (back to 7.3 days),
it should had not been in the server encodings. JOHAB's second byte
definitely contain 0x41 and above. *johab*.map just reflect the
fact. I think we should remove JOHAB from the server
At this time Postgresql is unable to guarentee that complex* referencial
integrity (RI) constraints can be enforced using standard (read non-C)
triggers or SQL. This is an unfortunate side-effect of the MVCC model,
as it allows multiple transactions to modify a snapshot of the data at a
certain
On Fri, 23 Mar 2007, Florian G. Pflug wrote:
Teodor Sigaev wrote:
For given schema and server's locale, it's possible to have several FTS
configurations, but the only one (with special flag enabled)
could be used as default. Current (active) FTS configuration contains
in GUC variable
* Bruce Momjian:
src/backend/port/dynloader/aix.c
* This is an unpublished work copyright (c) 1992 HELIOS Software GmbH
* 30159 Hannover, Germany
The company still exists, it seems. Have you tried to contact them?
See http://www.helios.de/about/email.phtml.
--
Florian
This feature (ability to add a message payload to a NOTIFY) is on the
TODO list and I had undertaken to implement it. However, pressure of
other work has conspired to make that difficult, and Abhijit Menon-Sen
recently very kindly offered to help out.
Therer was some discussion of
Oleg Bartunov wrote:
On Fri, 23 Mar 2007, Florian G. Pflug wrote:
Teodor Sigaev wrote:
For given schema and server's locale, it's possible to have several
FTS configurations, but the only one (with special flag enabled)
could be used as default. Current (active) FTS configuration contains
in
Andrew Dunstan wrote:
So, before an investment of any more time is made by either Abhijit or
myself, I would like to get confirmation that a) there is broad
agreement on the desirability of the feature
Yes, absolutely desirable.
and b) that there is broad
agreement on the general design
On Mon, 26 Mar 2007, Florian G. Pflug wrote:
Oleg Bartunov wrote:
On Fri, 23 Mar 2007, Florian G. Pflug wrote:
Teodor Sigaev wrote:
For given schema and server's locale, it's possible to have several FTS
configurations, but the only one (with special flag enabled)
could be used as default.
We have had several customers get bit by the 8.2.3 stats collector bug.
It is also starting to get reported in areas such as IRC. The really bad
thing about this bug is that you won't know what is wrong unless you
know where to look, PostgreSQL will just appear slow and tying up
resources.
I
Dave Page wrote:
Andrew Dunstan wrote:
So, before an investment of any more time is made by either Abhijit
or myself, I would like to get confirmation that a) there is broad
agreement on the desirability of the feature
Yes, absolutely desirable.
good ;-)
and b) that there is broad
Andrew Dunstan wrote:
Let's say we provide 100Kb for this (which is not a heck of a lot) ,
that the average notification might be, say, 40 bytes of name plus 60
bytes of message. Then we have room for about 1000 messages in the
queue. This would get ugly only if backend presumably in the
I'm not sure if this is a bug, missing feature, misunderstanding on my part?
I checked the TODO list and couldn't find anything on it.
I currently have a 750 million row table, indexes are 10 GB, so trying
to partition it.
The basic -
constraint_exclusion + exact match = OK
Alvaro Herrera wrote:
Andrew Dunstan wrote:
Let's say we provide 100Kb for this (which is not a heck of a lot) ,
that the average notification might be, say, 40 bytes of name plus 60
bytes of message. Then we have room for about 1000 messages in the
queue. This would get ugly only if
Am Montag, 26. März 2007 18:07 schrieb Joshua D. Drake:
I reiterate the question. Can we please package 8.2.4.
Sure, go ahead.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 7: You can help support the
Peter Eisentraut wrote:
Am Montag, 26. März 2007 18:07 schrieb Joshua D. Drake:
I reiterate the question. Can we please package 8.2.4.
Sure, go ahead.
Funny :). What can I do to help get 8.2.4 branched?
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
While experimenting with the proposed CREATE INDEX support with
HOT, I realized that SI invalidation are not sent properly for pg_index
updates.
I noticed the following comment in relcache.c
/*
* RelationReloadClassinfo - reload the pg_class row (only)
*
* This function is used only for
Pavan Deolasee [EMAIL PROTECTED] writes:
While experimenting with the proposed CREATE INDEX support with
HOT, I realized that SI invalidation are not sent properly for pg_index
updates.
Hmm ... actually, CREATE INDEX CONCURRENTLY gets this wrong already, no?
I suspect that sessions existing at
Joris Dobbelsteen [EMAIL PROTECTED] writes:
My intention is to expose the functionality to the outside world for
general use. This provides means to ensure custom complex constraints
can be enforced properly. I hope to push it into 8.3 if possible.
You are at least a month too late for 8.3,
Oleg Bartunov oleg@sai.msu.su writes:
On Fri, 23 Mar 2007, Florian G. Pflug wrote:
Isn't the real problem that only _one_ configuration per locale should
be marked as DEFAULT at any time, no matter what schema it is in?
I'm not sure I understand you correct (a bit complex :), but it's allowed
On 3/26/07, Tom Lane [EMAIL PROTECTED] wrote:
Hmm ... actually, CREATE INDEX CONCURRENTLY gets this wrong already, no?
I suspect that sessions existing at the time C.I.C is done will never
see the new index as valid, unless something else happens to make them
drop and rebuild their relcache
Alvaro Herrera [EMAIL PROTECTED] writes:
Why have the name on each message? Presumably names are going to be few
compared to the total number of messages, so maybe store the names in a
separate hash table and link them with a numeric identifier. That gives
you room for a lot more messages.
Pavan Deolasee [EMAIL PROTECTED] writes:
On 3/26/07, Tom Lane [EMAIL PROTECTED] wrote:
Hmm ... actually, CREATE INDEX CONCURRENTLY gets this wrong already, no?
Yes, C.I.C gets it wrong. I confirmed that new index is seen as invalid
for existing sessions. Is it something we should fix ?
On Wednesday 21 March 2007 09:07, Alvaro Herrera wrote:
Germán Poó Caamaño escribió:
I'm a student and I'm planning to submit a project for Google Summer of
Code. I would like to receive feedback about to implement the vacumm
scheduling in order to allow maintenance's windows.
I have
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
As a real-world example where the constraint cannot be enforced in
postgresql.
For every tuple t in cartridge_change, there must exists a tuple t' in
printers with t.id = t'.id, and a tuple t'' in cartridge_types with
t.color = t''.color
Joshua D. Drake wrote:
Funny :). What can I do to help get 8.2.4 branched?
There is no branching involved, but you can look into
src/tools/RELEASE_CHANGES and see what things you want to help with.
Getting a release changes list would be a start.
--
Peter Eisentraut
Andrew Dunstan wrote:
No loss, but, per previous discussion, it would block and try to get
other backends to collect their outstanding notifications.
Let's say we provide 100Kb for this (which is not a heck of a lot) ,
that the average notification might be, say, 40 bytes of name plus 60
Peter Eisentraut wrote:
Joshua D. Drake wrote:
Funny :). What can I do to help get 8.2.4 branched?
There is no branching involved, but you can look into
src/tools/RELEASE_CHANGES and see what things you want to help with.
Getting a release changes list would be a start.
We're just
On Mon, 2007-03-26 at 09:38 -0700, Weslee Bilodeau wrote:
mytest=# explain select count(*) from master where var_ts (
'2007-03-26 16:03:27.370627+00'::timestamptz - '1 month'::interval
)::timestamptz ;
If you're able to supply a constant value, why not subtract 1 month
before you submit the
Dave Page wrote:
Peter Eisentraut wrote:
Joshua D. Drake wrote:
Funny :). What can I do to help get 8.2.4 branched?
There is no branching involved, but you can look into
src/tools/RELEASE_CHANGES and see what things you want to help with.
Getting a release changes list would be a start.
On Mon, 26 Mar 2007, Tom Lane wrote:
Oleg Bartunov oleg@sai.msu.su writes:
On Fri, 23 Mar 2007, Florian G. Pflug wrote:
Isn't the real problem that only _one_ configuration per locale should
be marked as DEFAULT at any time, no matter what schema it is in?
I'm not sure I understand you
Joshua D. Drake wrote:
Dave Page wrote:
Peter Eisentraut wrote:
Joshua D. Drake wrote:
Funny :). What can I do to help get 8.2.4 branched?
There is no branching involved, but you can look into
src/tools/RELEASE_CHANGES and see what things you want to help with.
Getting a release changes
Joshua D. Drake wrote:
Dave Page wrote:
Peter Eisentraut wrote:
Joshua D. Drake wrote:
Funny :). What can I do to help get 8.2.4 branched?
There is no branching involved, but you can look into
src/tools/RELEASE_CHANGES and see what things you want to help with.
Getting a release changes
Simon Riggs wrote:
On Mon, 2007-03-26 at 09:38 -0700, Weslee Bilodeau wrote:
mytest=# explain select count(*) from master where var_ts (
'2007-03-26 16:03:27.370627+00'::timestamptz - '1 month'::interval
)::timestamptz ;
If you're able to supply a constant value, why not subtract 1 month
Hello,
Below is the change log as I see it. I gleaned it from here:
http://projects.commandprompt.com/public/pgsql/log/branches/REL8_2_STABLE
If I missed anything let me know.
Sincerely,
Joshua D. Drake
* Fixed preload_shared_libraries on Windows (Bruce)
* Rearrange use of
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: maandag 26 maart 2007 19:52
To: Joris Dobbelsteen
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Guarenteeing complex referencial
integrity through custom triggers
Joris Dobbelsteen [EMAIL PROTECTED] writes:
My
[Resent: mailing list only]
Tom, you mail server won't accept:
The e-mail system was unable to deliver the message, but did not report
a specific reason. Check the address and try again. If it still fails,
contact your system administrator.
orange.nl #5.0.0 X-SMTP-Server; host
Weslee Bilodeau wrote:
Mainly its because the value comes from a reporting system that has
minimal brains, it passes values it gets from the user directly into a
query.
IE, they enter '1 month', which I use to populate the interval value,
ts ( NOW() - $VALUE )
But, in the example I did
Neil Conway wrote:
Bruce Momjian wrote:
Someone has pointed out that the following files have the 4-part BSD
copyright, which includes the advertising clause:
src/backend/port/darwin/system.c
src/backend/port/dynloader/freebsd.c
src/backend/port/dynloader/openbsd.c
FYI, I have received permission, below, to remove the Andrew Yu
copyright. Thanks.
---
Andrew Yu wrote:
Hi Bruce,
This header is originally part of a separate library
package for dynamic loading on DECstation
On 3/26/07, Joshua D. Drake [EMAIL PROTECTED] wrote:
* Improve handling of psuedoconstants (Tom)
s/psuedoconstants/pseudoconstants/
And +1 to have 8.2.4 released soon. I recommend our customers to not
use 8.2 atm because of the stats problem.
--
Guillaume
---(end of
Andrew Dunstan [EMAIL PROTECTED] writes:
and b) that there is broad agreement on the general design (i.e. to use a
circular buffer in shared memory, of configurable size, to hold the
outstanding message queue).
Would it spill out to disk and expand (and shrink again) as required? Loss of
Bruce Momjian wrote:
FYI, I have received permission, below, to remove the Andrew Yu
copyright. Thanks.
Can't we just remove the file outright? The last release of Ultrix was
in 1995.
-Neil
---(end of broadcast)---
TIP 3: Have you
Bruce Momjian wrote:
Someone has pointed out to me that we have non-PostgreSQL/Berkeley
copyrights on a number of files:
src/port/rint.c
* Copyright (c) 1999, repas AEG Automation GmbH
src/backend/port/dynloader/aix.c
* This is an unpublished work
Neil Conway wrote:
Bruce Momjian wrote:
FYI, I have received permission, below, to remove the Andrew Yu
copyright. Thanks.
Can't we just remove the file outright? The last release of Ultrix was
in 1995.
Yea, but that was the easy one because I already knew the author and had
his
Patch withdrawn by author, perhaps reworked in the future.
---
Dany DeBontridder wrote:
Sorry I forgot the attach :-)
It is not perfect so bear with me, it is my first try.
Regards,
D.
On 3/21/07, Bruce Momjian
Luke Lonergan wrote:
I advocate the following:
- Enable specification of TOAST policy on a per column basis
As a first step, then:
- Enable vertical partitioning of tables using per-column specification of
storage policy.
How are these different from ALTER TABLE SET STORAGE? They
Simon, is this patch ready to be added to the patch queue? I assume not.
---
Simon Riggs wrote:
On Mon, 2007-03-12 at 09:14 +, Simon Riggs wrote:
On Mon, 2007-03-12 at 16:21 +0900, ITAGAKI Takahiro wrote:
With
Tatsuo,
Related to this, when are we going to get the Japanese po files in the
core distribution?
--Josh
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
Andrew Dunstan wrote:
Jeremy Drake wrote:
rsync -avzCH --delete rsync.postgresql.org::pgsql-cvs cvsroot/
The buildfarm howto has somewhat more complete instructions (including
how to adjust the various cvs config files if you need to). I set it up
the other day - took me about
Do we want to do anything about this for 8.3?
---
Jim C. Nasby wrote:
Yes, but if it was '2004-01-02 01:00:00'-'2004-01-01 00:00:00' it should
return 25:00:00, not 1 day 1:00.
I agree with Tom that this should be
Tatsuo,
Related to this, when are we going to get the Japanese po files in the
core distribution?
No idea. In my understanding, current message translating system has
serious problem if wrong locale and encoding is provided(has this
issue been solved in 8.3?). AFAIK Hiroki Kataoka, chairman
Tatsuo,
Related to this, when are we going to get the Japanese po files in the
core distribution?
No idea. In my understanding, current message translating system has
serious problem if wrong locale and encoding is provided(has this
issue been solved in 8.3?). AFAIK Hiroki Kataoka, chairman
Where are we on this? Peter thought the consistency makes sense, but if
we can provide functionality that doesn't require libxml, why not
do it?
---
Nikolay Samokhvalov wrote:
On 2/21/07, Alvaro Herrera [EMAIL PROTECTED]
Tatsuo Ishii [EMAIL PROTECTED] writes:
Related to this, when are we going to get the Japanese po files in the
core distribution?
No idea. In my understanding, current message translating system has
serious problem if wrong locale and encoding is provided(has this
issue been solved in 8.3?).
Tatsuo Ishii [EMAIL PROTECTED] writes:
Related to this, when are we going to get the Japanese po files in the
core distribution?
No idea. In my understanding, current message translating system has
serious problem if wrong locale and encoding is provided(has this
issue been solved in
Hi.
- Original Message -
From: Tom Lane [EMAIL PROTECTED]
Tatsuo Ishii [EMAIL PROTECTED] writes:
Related to this, when are we going to get the Japanese po files in the
core distribution?
No idea. In my understanding, current message translating system has
serious problem if
Teodor Sigaev wrote:
For given schema and server's locale, it's possible to have several FTS
configurations, but the only one (with special flag enabled)
could be used as default. Current (active) FTS configuration contains
in GUC variable tsearch_conf_name. If it's not defined, then FTS
On 3/23/07, Kevin Grittner [EMAIL PROTECTED] wrote:
[...]
That's the good news. The bad news is that I operate under a management
portability dictate which doesn't currently allow that syntax, since not all of
the products they want to
It doesn't really touch the substance, but I am
Hi,
Here's an update of a code to improve full page writes as proposed in
http://archives.postgresql.org/pgsql-hackers/2007-01/msg01491.php
and
http://archives.postgresql.org/pgsql-patches/2007-01/msg00607.php
Update includes some modification for error handling in archiver and
restoration
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
This also ties into the discussions we've had off-and-on about making
catalog lookups behave in an MVCC fashion instead of using SnapshotNow.
I'm still pretty hesitant to go there, but maybe we could do something
involving MVCC for unlocked
Andrew Dunstan [EMAIL PROTECTED] writes:
... But ISTM that means we just need to pick a few strategic spots
that will call CHECK_FOR_NOTIFICATIONS() even in the middle of a
transaction and store them locally.
Minor comment --- I don't believe in having a separate sprinkle of
notify-specific
Ühel kenal päeval, E, 2007-03-26 kell 14:07, kirjutas Tom Lane:
Alvaro Herrera [EMAIL PROTECTED] writes:
Why have the name on each message? Presumably names are going to be few
compared to the total number of messages, so maybe store the names in a
separate hash table and link them with a
75 matches
Mail list logo
