Tom Lane wrote:
> Bruce Momjian writes:
> > OK, I have a new patch, which simplifies the code by using
> > TrimTrailingZeros(), gives more consistent subsecond display, and
> > subpresses the rounding problem:
>
> Does anyone have any idea why the existing code is designed to keep the
> number of
Greg Sabino Mullane <[EMAIL PROTECTED]> writes:
> Attached is my "backslash consistency" patch which basically makes all
> the backslash commands behave as \dt does: \d* shows non-system objects,
> and \d*S shows system objects.
Could we have a way to turn this off? At least for functions and
ope
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Attached is my "backslash consistency" patch which basically makes all
the backslash commands behave as \dt does: \d* shows non-system objects,
and \d*S shows system objects. See the archives for more discussion on
this. I wrote this patch some tim
Jaime Casanova wrote:
i found out that the function textToQualifiedNameList doesn't use the
second argument it receive (caller). i suppose in the past was used
and now it is useless, if that is the case here is a patch removing.
Or are any reasons to keep that argument?
Applied to HEAD. Thanks
Tom Lane wrote:
Oliver Jowett <[EMAIL PROTECTED]> writes:
Here's a patch that adds four new GUCs:
tcp_keepalives (defaults to on, controls SO_KEEPALIVE)
tcp_keepalives_idle (controls TCP_KEEPIDLE)
tcp_keepalives_interval (controls TCP_KEEPINTVL)
tcp_keepalives_count (controls TCP_KEEPCN
Bruce Momjian writes:
> OK, I have a new patch, which simplifies the code by using
> TrimTrailingZeros(), gives more consistent subsecond display, and
> subpresses the rounding problem:
Does anyone have any idea why the existing code is designed to keep the
number of displayed fractional digits e
Michael Fuhr wrote:
> I'm getting time, timetz, and horology regression failures in HEAD
> on Solaris 9 / gcc 3.4.2. So are other machines in the build farm,
> such as this one:
>
> http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=shark&dt=2005-05-26%2004:21:00
>
> I'm getting the same regressi
Oliver Jowett <[EMAIL PROTECTED]> writes:
> Here's a patch that adds four new GUCs:
> tcp_keepalives (defaults to on, controls SO_KEEPALIVE)
> tcp_keepalives_idle (controls TCP_KEEPIDLE)
> tcp_keepalives_interval (controls TCP_KEEPINTVL)
> tcp_keepalives_count (controls TCP_KEEPCNT)
Do yo
Bruce Momjian writes:
> I am not very excited about adding four more GUC variables, and I am
> thinking we could just have it use the OS defaults and see if we need
> more later, so that would add only one GUC.
Huh? "Use the OS defaults" is where we are now.
I'm unconvinced of the value of allo
ITAGAKI Takahiro wrote:
The patch adds a new choice "open_direct" to wal_sync_method.
It uses O_DIRECT flags for WAL writes, like O_SYNC.
Have you looked at what the performance difference of this option is?
For example, these benchmark results seem to indicate that an older
version of the pa
Bruce Momjian wrote:
>
> Patch applied with adjustment --- the second part of your patch that
> skips comparing the first byte seemed unnecessary. It seemed likely
> to cause a cpu stall, so just doing the loop seemed faster.
>
> Did you test if the second part of your patch actually caused a spe
Dinesh Pandey wrote:
> Is this implementation is available in postgres 8.0.2 ? Or which
> version of Postgres?
At this time, it's not available anywhere.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 1:
Is this implementation is available in postgres 8.0.2 ? Or which version of
Postgres?
Thanks
Dinesh Pandey
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Pavel Stehule
Sent: Thursday, May 26, 2005 12:47 PM
To: Neil Conway
Cc: Bruce Momjian; pgsql-patch
This patch ticks off the following TODO items:
Consider use of open/fcntl(O_DIRECT) to minimize OS caching, especially for
WAL writes.
The patch adds a new choice "open_direct" to wal_sync_method.
It uses O_DIRECT flags for WAL writes, like O_SYNC.
I had sent a patch looked like this before
(
> I think the docs need more than just "these variables are set when an
> exception is raised".
>
> The patch current resets SQLSTATE and SQLERRM whenever a new block is
> entered. So:
>
> create function trap_exceptions() returns void as $_$
> begin
> begin
> raise exception 'first e
15 matches
Mail list logo