On 7/7/06, Andrew Dunstan [EMAIL PROTECTED] wrote:
Why is this better than using the service file?service file is not well described in manual. quick grep showed that we have PGSERVICE variable, and pg_service.conf.sample, which doesn't even include all possible parameter names.
and - comments in
On Jul 4, 2006, at 3:35 AM, Dave Page wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Neil Conway
Sent: 04 July 2006 05:53
To: pgsql-hackers@postgresql.org
Subject: [HACKERS] system info functions
(1) The docs claim that pg_get_viewdef() returns
ISTM that pg_dump needs to produce output that includes schema names,
though I'm not sure what side-effects that would have. I know one
issue is that it'd make it next to impossible to move things to a
different schema just be editing the dump.
On Jul 5, 2006, at 9:47 AM, Phil Frost wrote:
On 7/7/06, Martijn van Oosterhout kleptog@svana.org wrote:
Something I've been thinking of while reading this thread. One bigdisadvantage of doing it in the backend is that your methods ofreturning data are limited. Your resultset can only return one type.
For example, if you start decoding all
hubert depesz lubaczewski wrote:
On 7/7/06, *Andrew Dunstan* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Why is this better than using the service file?
service file is not well described in manual. quick grep showed that
we have PGSERVICE variable, and pg_service.conf.sample,
On Jul 6, 2006, at 11:02 AM, Phil Frost wrote:
I hope the above example is strong enough to elicit a comment from a
qualified developer. If it is not, consider that stored procedures
contain prepared statements, and many client applications cache
prepared
statements as well. Thus, revoking
On Jul 6, 2006, at 4:02 PM, Thomas Hallgren wrote:
In answer to your question, though my opinion carries no special
weight at
all, I would suggest adding a bare bones 16-byte data type to core
and a
second binary-compatible data type based on it that parsed/output
as uuids.
The extended
.\src\bin\psql\print.c(1912): warning C4090: 'function' : different
'const' qualifiers
.\src\bin\psql\print.c(1913): warning C4090: 'function' : different
'const' qualifiers
Variables are declared const, are you really supposed to pass that to
free()? Cast at free()? Remove const?
//Magnus
On Saturday 08 July 2006 14:54, Jim Nasby wrote:
On Jul 6, 2006, at 4:02 PM, Thomas Hallgren wrote:
In answer to your question, though my opinion carries no special
weight at
all, I would suggest adding a bare bones 16-byte data type to core
and a
second binary-compatible data type
