Alvaro Herrera [EMAIL PROTECTED] writes:
What about arranging postmaster's main loop so that it starts the stats
collector process if one of the options is activated (assuming they were
all off at start)? Right now you have to restart the server, but I
don't see why it has to be like that.
Petr
Jelinek wrote:
This patch fixes pg_stat_database which is
broken since this commit: http://archives.postgresql.org/pgsql-committers/2005-05/msg00126.php
Neilc forgot to add new db entry inicialization to
pgstat_recv_bestart() when he removed it from pgstat_add_backend()
function,
Stephen Frost [EMAIL PROTECTED] writes:
Attached please find files and patches associated with moving from the
User/Group system currently in place to Roles, as discussed
previously.
I have cleaned this up a bit and committed it. I normally wouldn't
commit an incomplete patch, but this
Tom Lane wrote:
Actually, this entire thread is based on a misconception: the bug
reporter was under the misimpression that the sum total of what the
collector does is described by the three suboptions, and so having
start_collector on without any of the suboptions on is a useless state.
But
Hi,
I attached second try of per-database and per-user connection limit for
your review.
This time I am using information stored in ProcArray to get number of
connections - I modified PGPROC struct to also include userid.
Limits for user and database are stored in catalog tables. This
Luke, Alon
OK, I'm going to apply the patch to my copy and try to get my head
around it. meanwhile:
. we should not be describing things as old or new. The person
reading the code might have no knowledge of the history, and should not
need to.
. we should not have slow and fast either. We
Bruce Momjian wrote:
Andrew Dunstan wrote:
I'm very glad to see this. But is a nicer name possible? To perl
programmers at least, substitute should make sense.
What is the matter with replace? We already have replace:
test= \df replace
List of functions
Atsushi Ogawa wrote:
I think that regexp_replace is a good name. It is easy to understand.
I'll go with the flow.
cheers
andrew
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Bruce Momjian pgman@candle.pha.pa.us writes:
My issue is that we usually don't have GUC variables that can be set
automatically. Why can't we have the stats collector try to start, and
just throw a server log message if it fails.
I still say the code is not broken and does not require fixing.
On 06/27/2005 10:03:06 PM, Karl O. Pinc wrote:
On 06/27/2005 08:34:19 PM, Michael Fuhr wrote:
On Tue, Jun 28, 2005 at 01:54:08AM +, Karl O. Pinc wrote:
On 06/27/2005 06:33:03 PM, Michael Fuhr wrote:
See timeofday().
That only gives you the time at the start of the transaction,
so you
There's no time to do this for 8.1, but I'd like to get it on
the books for
8.2:
The Problem: Occassionally a DBA needs to dump a database to a new
encoding. In instances where the current encoding, (or lack of an
encoding, like SQL_ASCII) is poorly supported on the target
database
On Tue, Jun 28, 2005 at 10:24:19PM +0200, Magnus Hagander wrote:
I *think* that's easy enough to do in time for 8.1. Trivial patch
attached. I hope it's enough :-) It passed my very quick testing...
(Yup, I read the mails aobut PGCLIENTENCODING, but an option to pg_dump
is certainly easier)
I *think* that's easy enough to do in time for 8.1. Trivial patch
attached. I hope it's enough :-) It passed my very quick testing...
(Yup, I read the mails aobut PGCLIENTENCODING, but an option to
pg_dump is certainly easier)
You forgot to document the long option, I think.
Oops.
I *think* that's easy enough to do in time for 8.1. Trivial patch
attached. I hope it's enough :-) It passed my very quick testing...
(Yup, I read the mails aobut PGCLIENTENCODING, but an option to
pg_dump is certainly easier)
You forgot to document the long option, I think.
Are
Alvaro Herrera wrote:
On Tue, Jun 28, 2005 at 10:24:19PM +0200, Magnus Hagander wrote:
I *think* that's easy enough to do in time for 8.1. Trivial patch
attached. I hope it's enough :-) It passed my very quick testing...
(Yup, I read the mails aobut PGCLIENTENCODING, but an option to
On Mon, Jun 27, 2005 at 09:08:05PM -0400, Bruce Momjian wrote:
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
It will be applied as soon as one of the PostgreSQL committers reviews
and approves it.
Please use
Luke Lonergan wrote:
Patch to update pgindent with new symbols and fix a bug in an awk section
(extra \\ in front of a ')').
Yea, that '\' wasn't needed. I applied the following patch to use //
instead of for patterns, and removed the unneeded backslash.
I will update the typedefs in a
On Tue, Jun 28, 2005 at 02:28:11PM -0400, Andrew Dunstan wrote:
Jim C. Nasby wrote:
All the logs for the most recent run against HEAD are now at
http://stats.distributed.net/~buildfarm/
A quick look shows that when you use --with-libraries=/foo/bar the
generated link line
Dave Page wrote:
The attached patch integrates dbsize functions into the backend, as per
discussion on -hackers. The following functions are included:
pg_relation_size(text) - Get relation size by name/schema.name
pg_relation_size(oid)- Get relation size by OID
Patch applied. Thanks.
---
Victor Y. Yegorov wrote:
Improved words spacing.
--
Victor Y. Yegorov
[ Attachment, skipping... ]
---(end of broadcast)---
TIP 7:
Patch applied. Thanks. Your documentation changes can be viewed in
five minutes using links on the developer's page,
http://www.postgresql.org/developer/testing.
---
Karl O. Pinc wrote:
On 06/27/2005 10:03:06 PM,
21 matches
Mail list logo
