On Mon, Apr 02, 2007 at 10:01:44PM -0400, Alvaro Herrera wrote:
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
Greg Smith wrote:
This patch puts entries in the log file around some backend events
that regularly cause client pauses, most of which are visible only
when running with log_min_messages = debug2.
Something that is aimed at a user should not be enabled at a debug
level. Debug levels are for
David Fetter [EMAIL PROTECTED] writes:
On Mon, Apr 02, 2007 at 10:01:44PM -0400, Alvaro Herrera wrote:
So, hum, what happened to the idea of creating the array types only
on demand?
Scotched, as far as I could tell,
More like you submitted a patch that entirely ignores multiple people's
New commands:
CLOSE ALL -- close all cursors
DEALLOCATE ALL -- close all prepared stmts
RESET PLANS-- drop all plans
RESET TEMP | TEMPORARY -- drop all temp tables
RESET SESSION -- drop/close/free everything
So
On Mon, 2007-04-02 at 19:10 -0400, Bruce Momjian wrote:
Where is the final version of this patch? What patches are stuck in the
patch moderator queue?
We already discussed the dependency that exists with this patch and you
accepted that.
--
Simon Riggs
EnterpriseDB
Here's third revision of WAL archival optimization patch. GUC
parameter name was changed to wal_add_optimization_info.
Regards;
--
Koichi Suzuki
20070403_pg_lesslog.tar.gz
Description: application/gzip
---(end of broadcast)---
TIP 1: if
Bruce Momjian wrote:
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
Thank you very much for including. Attached is an update of the patch
according to Simon Riggs's comment about GUC name.
Regards;
--
Koichi
On Mon, Apr 02, 2007 at 09:06:17PM -0400, Bruce Momjian wrote:
Michael, is there any progress on this?
---
So this essantially is only to get an error message into the connection
structure. However, having an empty
On a busy system, checkpoint could be starved while queuing for the
CheckpointStartLock. To avoid that, get rid of CheckpointStartLock and
instead set a flag in PGPROC struct when a commit starts. After
computing the REDO ptr, checkpoint waits for all backends that had that
flag set to finish
On Tue, Apr 03, 2007 at 02:30:07AM -0400, Tom Lane wrote:
David Fetter [EMAIL PROTECTED] writes:
On Mon, Apr 02, 2007 at 10:01:44PM -0400, Alvaro Herrera wrote:
So, hum, what happened to the idea of creating the array types
only on demand?
Scotched, as far as I could tell,
More like
Simon Riggs wrote:
On Mon, 2007-04-02 at 19:10 -0400, Bruce Momjian wrote:
Where is the final version of this patch? What patches are stuck in the
patch moderator queue?
We already discussed the dependency that exists with this patch and you
accepted that.
Oh, that was the patch. I
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.
---
On Tue, 3 Apr 2007, Peter Eisentraut wrote:
Something that is aimed at a user should not be enabled at a debug
level. Debug levels are for debugging, not for very high verbosity.
I asked for feedback about where to log at when I intially sent the first
version of this in and didn't hear
Tom Lane wrote:
David Fetter [EMAIL PROTECTED] writes:
On Mon, Apr 02, 2007 at 10:01:44PM -0400, Alvaro Herrera wrote:
So, hum, what happened to the idea of creating the array types only
on demand?
Scotched, as far as I could tell,
More like you submitted a patch that entirely
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.
---
On Tue, 2007-04-03 at 15:04 +0100, Heikki Linnakangas wrote:
Simon Riggs wrote:
Here's the next version (v10) of the patch, ready for review.
Thanks for reviewing.
I've struggled with what to call all of the new concepts inherent in
this patch, but I think I've got something now. COMMIT
FAST PostgreSQL wrote:
Am Dienstag, 3. April 2007 20:33 schrieb FAST PostgreSQL:
Attached is the completed patch for the COPY-able sql log outputs.
Could you please remove random whitespace changes from this patch?
Done and attached.
Brief review of the CSV aspect only:
Tom Lane wrote:
Heikki Linnakangas [EMAIL PROTECTED] writes:
On a busy system, checkpoint could be starved while queuing for the
CheckpointStartLock. To avoid that, get rid of CheckpointStartLock and
instead set a flag in PGPROC struct when a commit starts. After
computing the REDO ptr,
A doc patch to add an example of what an invalid index looks like in psql, as
requested by a commenter and Bruce.
Index: doc/src/sgml/ref/create_index.sgml
===
RCS file:
On Mon, Apr 02, 2007 at 07:25:46PM -0400, Bruce Momjian wrote:
I assume this patch is not ready for 8.3, so I added a URL to the TODO
list for it.
I have reworked it such that it ignores custom variable templates as Tom
suggested. Attached is the new version.
Joachim
Index:
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.
---
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.
---
stark wrote:
A doc patch to add an example of
On Wed, 4 Apr 2007 02:26, Andrew Dunstan wrote:
I am currently doing the following modifications to the patch as per the
review comments.
1. Changing all references to 'sqllog' or 'sql' to 'csvlog' and 'csv'
respectively.
2. Escaping the username and databasename
3. Constructing the csvlog
On Mon, 2 Apr 2007 03:15, Simon Riggs wrote:
Cool patch.
On Wed, 2007-04-04 at 18:36 +, FAST PostgreSQL wrote:
The planner has to be taught to treat a DELETE/UPDATE WHERE CURRENT OF
as a TidScan. Currently it follows the sequential scan route and
extracts the current tuple based on
On 4/2/07, Bruce Momjian [EMAIL PROTECTED] wrote:
This has been saved for the 8.4 release:
http://momjian.postgresql.org/cgi-bin/pgpatches_hold
mmm... sorry, i have been busy... how many time we have? i can send
something for friday...
--
regards,
Jaime Casanova
Programming today
25 matches
Mail list logo
