This has been saved for the 8.1 release:
http:/momjian.postgresql.org/cgi-bin/pgpatches2
---
Simon Riggs wrote:
> On Sat, 2005-01-01 at 17:47, Simon Riggs wrote:
> > On Sat, 2005-01-01 at 17:01, Bruce Momjian wrote:
This has been saved for the 8.1 release:
http:/momjian.postgresql.org/cgi-bin/pgpatches2
---
Stephen Frost wrote:
> * Tom Lane ([EMAIL PROTECTED]) wrote:
> > Stephen Frost <[EMAIL PROTECTED]> writes:
> > > Ok, shoul
This has been saved for the 8.1 release:
http:/momjian.postgresql.org/cgi-bin/pgpatches2
---
Hans-Juergen Schoenig wrote:
> Folks,
>
> We have implemented SELECT FOR UPDATE NOWAIT for PostgreSQL.
> The patch attach
Wow, yea, that is long. Not sure where that should go.
---
Mark Kirkwood wrote:
> I have always thought that an example of how to maintain a summary table
> via triggers would be nice... but until the other day, had not at
This has been saved for the 8.1 release:
http:/momjian.postgresql.org/cgi-bin/pgpatches2
---
Stephen Frost wrote:
> Greetings,
>
> Small patch to move get_grosysid() from catalog/aclchk.c to
> utils/cache/lsys
Hi,
While playing around, I got the following error message:
--
FATAL: pre-existing shared memory block (key 5432001, ID 90898435) is
still in use
HINT: If you're sure there are no old server processes still running,
remove the shared memory block with the command "ipcrm", or just delete
the f
Tom Lane wrote:
Fair point, but you could make the same argument against *any* side
effect of RESET CONNECTION. You're just complaining about PREPARE
because you can see immediately where that breaks JDBC. Anything that
any driver does to set up per-connection state the way it wants will
be equal
Oliver Jowett <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Maybe the RESET CONNECTION command
>> should have an option whether to zap prepared statements or not?
> That doesn't really help the JDBC driver case. The problem is that there
> are prepared statements that have been set up by the d
Tom Lane wrote:
Kris Jurka <[EMAIL PROTECTED]> writes:
Also I don't like the idea of cleaning up prepared statements.
Hmm. This seems a bit eye-of-the-beholder-ish, ie you could make a
legitimate argument either way. Maybe the RESET CONNECTION command
should have an option whether to zap prepare
Resending to the correctly-spelled list alias. Why does postgresql.org
not generate bounces for unknown addresses, anyway?
Original Message
Subject: Re: [PATCHES] Implementing RESET CONNECTION ...
Date: Tue, 04 Jan 2005 13:58:44 +1300
From: Oliver Jowett <[EMAIL PROTECTED]>
To:
Todd Kover <[EMAIL PROTECTED]> writes:
> The attached patch adds a directive to the config file,
> krb_server_hostname that allows the hostname that service tickets are
> obtained against to be different from the hostname of the db server.
Why is this necessary? If it is necessary, wouldn't somet
Kris Jurka <[EMAIL PROTECTED]> writes:
> On Thu, 30 Dec 2004, [ISO-8859-1] Hans-Jürgen Schönig wrote:
>> We have implemented a patch which can be used by connection pools for
>> instance. RESECT CONNECTION cleans up a backend so that it can be
>> reused. Temp tables, LISTEN / NOTIFY stuff, WITH HOL
This update replaces the previous patch for the psql logfile option
The print.c routine is also built into src/bin/scripts
The ifdef USE_LOGFILE wrapper is to keep out compile errors when the
routine is linked into programs other than psql
Lorne
--
-
It does happen all over the place...
I have equivalent $(X) patches to all the makefiles in src/bin and below
Lorne
In <[EMAIL PROTECTED]>, on 01/03/05
at 10:47 PM, Peter Eisentraut <[EMAIL PROTECTED]> said:
>[EMAIL PROTECTED] wrote:
>> NOTE - the patch to the makefile is to keep it from co
This has been saved for the 8.1 release:
http:/momjian.postgresql.org/cgi-bin/pgpatches2
---
Euler Taveira de Oliveira wrote:
> Hi,
>
>
> > > > This patch just implement a function that returns the uptime of
> >
Simon Riggs wrote:
> Here's my bgwriter instrumentation patch, which gives info that could
> allow the bgwriter settings to be tuned.
Uh, what does this do exactly? Add additional logging output?
--
Bruce Momjian| http://candle.pha.pa.us
pgman@candle.pha.pa.us
On Mon, 2005-01-03 at 23:03, Bruce Momjian wrote:
> Simon Riggs wrote:
> > On Mon, 2005-01-03 at 20:09, Bruce Momjian wrote:
> > > OK, we have a submitted patch that attempts to improve bgwriter by
> > > making bgwriter_percent control what percentage of the buffer is
> > > scanned.
> > >
> > > Th
The attached patch adds a directive to the config file,
krb_server_hostname that allows the hostname that service tickets are
obtained against to be different from the hostname of the db server.
We use this because the db server binds to a specific ip address which
has a name that's different from
Simon Riggs wrote:
> On Mon, 2005-01-03 at 20:09, Bruce Momjian wrote:
> > OK, we have a submitted patch that attempts to improve bgwriter by
> > making bgwriter_percent control what percentage of the buffer is
> > scanned.
> >
> > The patch still needs doc changes and a change to the default valu
On Mon, 2005-01-03 at 20:09, Bruce Momjian wrote:
> OK, we have a submitted patch that attempts to improve bgwriter by
> making bgwriter_percent control what percentage of the buffer is
> scanned.
>
> The patch still needs doc changes and a change to the default value but
> at this point we need a
Guillaume LELARGE wrote:
> Sorry to give these separately... postgres-fr.po is due to a
> translation error, pg_ctl-fr.po is an update.
Installed.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 2: you can
On Mon, 3 Jan 2005, [UTF-8] Hans-JÃrgen SchÃnig wrote:
> I have seen that the JDBC driver is doing some GUC settings.
> However, this does not prevent you from bad users who change GUCs for
> some reason.
Actually it does. The V3 protocol provides a ParameterStatus message that
notifies us wh
Kris,
I have seen that the JDBC driver is doing some GUC settings.
However, this does not prevent you from bad users who change GUCs for
some reason. It might very well happen that a user sets the DateStyle to
some different value temporarily. A different program would in this case
behave RANDOM
On Mon, 3 Jan 2005, Bruce Momjian wrote:
OK, we have a submitted patch that attempts to improve bgwriter by
making bgwriter_percent control what percentage of the buffer is
scanned.
The patch still needs doc changes and a change to the default value but
at this point we need a vote on the patch. I
[EMAIL PROTECTED] wrote:
> NOTE - the patch to the makefile is to keep it from constantly
> building psql.exe as the target "psql" all by itself is never created
> as the output executable on OS/2 and Windows is psql.exe.
If this were a problem on Windows, we'd have more problems all over the
pla
On Thu, 30 Dec 2004, [ISO-8859-1] Hans-Jürgen Schönig wrote:
> We have implemented a patch which can be used by connection pools for
> instance. RESECT CONNECTION cleans up a backend so that it can be
> reused. Temp tables, LISTEN / NOTIFY stuff, WITH HOLD cursors, open
> transactions, prepared
Bruce Momjian writes:
> OK, we have a submitted patch that attempts to improve bgwriter by
> making bgwriter_percent control what percentage of the buffer is
> scanned.
> The patch still needs doc changes and a change to the default value but
> at this point we need a vote on the patch. Is it:
OK, we have a submitted patch that attempts to improve bgwriter by
making bgwriter_percent control what percentage of the buffer is
scanned.
The patch still needs doc changes and a change to the default value but
at this point we need a vote on the patch. Is it:
* too late for 8.0
Here is a patch that allows psql to create a session log
NOTE - the patch to the makefile is to keep it from constantly building
psql.exe as the target "psql" all by itself is never created as the output
executable on OS/2 and Windows is psql.exe.
The patch provides for a new command line argume
29 matches
Mail list logo
