PQmakeEmptyPGresult() will return NULL if malloc() fails for required
PGresult struct.
Index: doc/src/sgml/libpq.sgml
===
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/libpq.sgml,v
retrieving revision 1.184
diff -u -c -r1.184
This post includes dbsize backend integration and Server
instrumentation: pg_terminate_backend, pg_reload_conf
Server instrumentation functions included:
pg_tablespace_size()
pg_database_size()
pg_relation_size()
pg_size_pretty()
well-known from contrib/dbsize, waiting in unapplied patches
Andreas Pflug [EMAIL PROTECTED] writes:
pg_terminate_backend()
exposing kill -SIGTERM backendpid to the client
The objections to this have not changed since last year; in fact they
are stronger because we have at least one report of actual trouble
with retail SIGTERMs.
pg_file_stat()
Tom Lane wrote:
Andreas Pflug [EMAIL PROTECTED] writes:
pg_terminate_backend()
exposing kill -SIGTERM backendpid to the client
The objections to this have not changed since last year; in fact they
are stronger because we have at least one report of actual trouble
with retail SIGTERMs.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane
Sent: 10 June 2005 14:52
To: Andreas Pflug
Cc: PostgreSQL-patches
Subject: Re: [PATCHES] Server instrumentation
pg_file_stat()
pg_file_length()
pg_file_read()
pg_file_write()
Andreas Seltenreich wrote:
Hi,
the following patch makes the filename used to store the readline
history customizable through a variable named HISTFILE, analogous to
psql's already implemented HISTCONTROL and HISTSIZE variables, and
bash's HISTFILE-Variable.
The motivation was to be able
It seems the plperl code has changed in the areas you are modifying.
Would you update your patch against current CVS? Thanks.
---
David Kamholz wrote:
Hello,
Here's a patch I added against plperl, originally against
Andreas Seltenreich wrote:
Bruce Momjian schrob:
I noticed your documentation example had a space before :DBNAME --- I
removed the space.
This space is necessary for proper expansion of the parameter. The
\set-Command concatenates all its arguments after expansion:
Tom Lane wrote:
A nonterminal that is not intended to represent any real input, ever,
is just plain weird.
If you say so... PL/PgSQL already uses such a beast, though: the lno
nonterminal, for example.
Not at all. The right way to do this, I think, is for the mid-rule
action to palloc the
Tatsuo Ishii [EMAIL PROTECTED] writes:
In mic_to_euc_jp(), the call of mic2sjis() is a mistake.
It is necessary to call mic2euc_jp() here.
Thanks. The bug was there since 7.3. Apparently nobody uses
MIC-EUC_JP conversion (This is not surprising since very few people
use Mule
Hi Tatsuo,
On Sat, 11 Jun 2005, Tatsuo Ishii wrote:
If you agree that it's wrong, please do back-patch (at least 8.0,
and personally I'd fix it back to 7.3).
I will do it later (now is 2:00 AM and I need to go to bed...)
This was an easy one:
http://postgresql.gunduz.org/patches/
have
* Bruce Momjian (pgman@candle.pha.pa.us) wrote:
I am removing this patch from the queue because without the role
feature I don't think it makes sense to rename the grammer tokens.
Sure. I've rolled this patch into my role tree so these changes will be
included when the CREATE ROLE, etc is
12 matches
Mail list logo
