to pgAdmin, and
doesn't require that we instruct users to install more server side
plugin code to use the features they want.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http
an optional format that pgAdmin
could request with appropriate grammar, it would be something that was
only available if the plugin was loaded, and would replace regular
EXPLAIN output? If so, that would be extremely inconvenient, and next
to useless for general purpose utilities.
--
Dave Page
or information
gathering tool more or less impossible to write.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches
On Sat, May 3, 2008 at 12:24 AM, Alvaro Herrera
[EMAIL PROTECTED] wrote:
Dave Page wrote:
Hi,
The attached patch implements a new function, pg_get_keywords(), which
returns a set of records describing the keywords recognised by the
server. This allows clients such as pgAdmin to get
| Type or function name
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
Index: doc/src/sgml/func.sgml
===
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/func.sgml,v
retrieving revision 1.434
diff -c -r1.434 func.sgml
On Sat, May 3, 2008 at 9:06 PM, Tom Lane [EMAIL PROTECTED] wrote:
Dave Page [EMAIL PROTECTED] writes:
Attached is an updated patch, giving the following output.
Oh, one other thing: dropping externs into random modules unrelated to
their source module is completely awful programming style
| Unreserved
(372 rows)
I wasn't sure about the best way to describe the categories -
obviously they need to be non-translatable (for client software to
interpret), but human readable is also nice. I'm happy to hear
alternate suggestions.
--
Dave Page
EnterpriseDB UK: http
(please nudge me if I miss
it).
--
Dave Page
EnterpriseDB UK Ltd: http://www.enterprisedb.com
PostgreSQL UK 2008 Conference: http://www.postgresql.org.uk
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
On Fri, Feb 29, 2008 at 6:41 PM, Magnus Hagander [EMAIL PROTECTED] wrote:
Will you provide a patch for that, or should I? (I remind you I have no
box ready to reproduce it on, so it helps a lot if you can do it :-P)
Patch attached. Tested on XP and Vista.
--
Dave Page
EnterpriseDB UK Ltd
tests, no?
Yeah, that should do it.
Meanwhile, I'll apply what we have with my additios and cleanups per mine
and Heikkis comments, because they fix the most important codepaths.
Thanks for putting the final polish on this.
--
Dave Page
EnterpriseDB UK Ltd: http://www.enterprisedb.com
PostgreSQL
process. This remains
secure because administrative privileges are granted to the groups
that we've dropped, not the user itself.
I've tested on Vista and XP, but additional testing would be useful
(Andrew, Magnus?). Please apply to head, 8.3 and 8.2
--
Dave Page
EnterpriseDB UK: http
On Jan 28, 2008 12:51 PM, Pavel Stehule [EMAIL PROTECTED] wrote:
Hello
this patch define new function flag - OBFUSCATE. With this flag
encrypted source code is stored to probin column. Password is stored
in GUC_SUPERUSER_ONLY item - it is similar security like SQL Server
does (where
On Jan 28, 2008 2:26 PM, Pavel Stehule [EMAIL PROTECTED] wrote:
sure, but do you know, Tom dislikes new columns in pg_proc :).
Tom doesn't seem to like the idea of obfuscation of function code much
either :-)
This
patch is usable sample of one possible solution and doesn't need
initdb. And
On 18/01/2008, Peter Eisentraut [EMAIL PROTECTED] wrote:
Tom Lane wrote:
What would work better is to add some code that checks whether
pg_control_version looks like the byte-swap of a small number,
and prints a suitably modified error message if so.
Here is a possible patch. Example
On 08/01/2008, Magnus Hagander [EMAIL PROTECTED] wrote:
On Thu, Dec 20, 2007 at 10:02:24AM +0900, Hiroshi Saito wrote:
A question there though - do we care about the length of time_t on client
platforms, or should we instead just disable the whole check for the
client? AFAICS we don't expose
Tom Lane wrote:
Dave Page [EMAIL PROTECTED] writes:
Alvaro Herrera wrote:
I think you could get the same effect by putting the -W in PGOPTIONS (in
pgbench's environment).
That's a good point. It does have the downside that it will affect the
pgbench results - though that wouldn't actually
Dave Page wrote:
Tom Lane wrote:
Dave Page [EMAIL PROTECTED] writes:
Gregory Stark wrote:
An alternative is leaving it in the project file but putting
something like
this in c.h:
Put it in win32.h, please. c.h shouldn't get cluttered with
platform-specific kluges when there's no need
Whilst doing some profiling of the server I found it useful to add an
option to pgbench to introduce a delay between client connection setup
and the start of the benchmark itself to allow me time to attach the
profiler to one of the backends.
Attached is the patch in case anyone finds a use for
Neil Conway wrote:
On Mon, 2007-12-10 at 19:27 +, Dave Page wrote:
Whilst doing some profiling of the server I found it useful to add an
option to pgbench to introduce a delay between client connection setup
and the start of the benchmark itself to allow me time to attach the
profiler
Alvaro Herrera wrote:
Dave Page wrote:
I'm aware of postgres -W, but wanted something that wouldn't get in the
way of other connections and would only affect my pgbench tests.
I think you could get the same effect by putting the -W in PGOPTIONS (in
pgbench's environment).
That's a good
Tom Lane wrote:
Dave Page [EMAIL PROTECTED] writes:
[ get rid of wsprintf in favor of snprintf ]
+1 for not depending on nonstandard subroutines without need.
But please note the standard locution is snprintf(buf, sizeof(buf), ...
Not sizeof() - 1.
Noted.
!char*tmppath=0
Tom Lane wrote:
[ looks again... ] Actually, I think you just proved my point for me.
The ZeroMemory call should go away, no?
Yup, quite correct. v3 attached.
/D
Index: src/backend/port/win32/signal.c
===
RCS file:
Gregory Stark wrote:
Tom Lane [EMAIL PROTECTED] writes:
! /*
! * Note: We use getenv here because the more modern
SHGetSpecialFolderPath()
! * will force us to link with shell32.lib which eats valuable desktop
heap.
! */
! tmppath = getenv(APPDATA);
Hmm, is
The attached patch adds some missing Windows codepage numbers to the
table in chklocale.c.
Regards, Dave.
*** src/port/chklocale.c.orig Wed Oct 3 18:16:39 2007
--- src/port/chklocale.c Wed Oct 10 12:30:05 2007
***
*** 72,97
--- 72,103
{PG_UTF8, UTF-8},
{PG_UTF8,
Magnus Hagander wrote:
Yes, that was the problem. Attached patch fixes the problem for me on
Windows and Linux using the error mark functionality. It seems a lot
cleaner than the other option.
Dave - can you test this one? Assuming that works, I'll go ahead and apply
it.
Yep, looks good
--- Original Message ---
From: Tom Lane [EMAIL PROTECTED]
To: Dave Page [EMAIL PROTECTED]
Sent: 29/09/07, 01:28:09
Subject: Re: [PATCHES] OpenSSL Applink
I concur with Magnus that it'll be better if there's not two code paths
here. It's not entirely clear whether BIO_new_fp
Tom Lane wrote:
Dave Page [EMAIL PROTECTED] writes:
From: Tom Lane [EMAIL PROTECTED]
... It's not entirely clear whether BIO_new_fp() would avoid the
problematic calls, but it doesn't look like it'd be hard to try.
The last version of the patch I posted uses BIO_new_file() in all cases
On Windows the OpenSSL guys have included code with 0.9.8 and above to
allow OpenSSL to work correctly regardless of the MSVC runtime libraries
that have been used with the host application. This has become noticable
with the MSVC++ build in which any client apps that connect using libpq
with a
Andrew Dunstan wrote:
Then I think I'd rather disable use of client certs for the offending
openssl versions in libpq, or let the apps die and refer the customers
to the openssl people to lobby them for a sane solution.
If this were 8.0 I'd agree, but thats not a nice solution for those
Andrew Dunstan wrote:
Dave Page wrote:
I believe we just didn't notice it until now because the older Mingw
builds use the MSVC 6.0 runtimes which just happened to be compatible
with the OpenSSL binary builds (we're now using 8.0), in addition to
which there are relatively few people
Tom Lane wrote:
Dave Page [EMAIL PROTECTED] writes:
The server doesn't seem to be affected, but the attached patch fixes the
problem for the client apps. Unfortunately it must be included in the
app itself, and not libpq.
This is pretty much in the category of they've got to be kidding
Heikki Linnakangas wrote:
Dave Page wrote:
Andrew Dunstan wrote:
Dave Page wrote:
I believe we just didn't notice it until now because the older Mingw
builds use the MSVC 6.0 runtimes which just happened to be compatible
with the OpenSSL binary builds (we're now using 8.0), in addition
Marko Kreen wrote:
On 9/28/07, Tom Lane [EMAIL PROTECTED] wrote:
Dave Page [EMAIL PROTECTED] writes:
Andrew Dunstan wrote:
Then I think I'd rather disable use of client certs for the offending
openssl versions in libpq, or let the apps die and refer the customers
to the openssl people
Tom Lane wrote:
Dave Page [EMAIL PROTECTED] writes:
Andrew Dunstan wrote:
Then I think I'd rather disable use of client certs for the offending
openssl versions in libpq, or let the apps die and refer the customers
to the openssl people to lobby them for a sane solution.
If this were 8.0
Tom Lane wrote:
Dave Page [EMAIL PROTECTED] writes:
Tom Lane wrote:
Doesn't really matter. Even if we were willing to hack our own client
apps like that (which I'm not), we can *not* transfer such a requirement
onto every libpq-using application. It's just not acceptable.
*We're
Dave Page wrote:
I did stumble across this text on a mailing list in response to someone
with a similar problem in some JNI code. I know little of the OpenSSL
API, but perhaps it rings bells with you before I spend my evening
trying to figure it out?
OK, I think I've figured out a fix
Dave Page wrote:
Dave Page wrote:
I did stumble across this text on a mailing list in response to someone
with a similar problem in some JNI code. I know little of the OpenSSL
API, but perhaps it rings bells with you before I spend my evening
trying to figure it out?
OK, I think I've
Magnus Hagander wrote:
Dave Page wrote:
Dave Page wrote:
Dave Page wrote:
I did stumble across this text on a mailing list in response to someone
with a similar problem in some JNI code. I know little of the OpenSSL
API, but perhaps it rings bells with you before I spend my evening
trying
Magnus Hagander wrote:
Hrrm. Obviously, I need to go sleep now. Sorry about that.
But it'd be nice to get rid of all those #ifdef blocks..
See the attached revision. This is untested as I don't have a linux box
to hand, but I believe it's right.
/D
Index: src/interfaces/libpq/fe-secure.c
Dave Page wrote:
Magnus Hagander wrote:
Hrrm. Obviously, I need to go sleep now. Sorry about that.
But it'd be nice to get rid of all those #ifdef blocks..
See the attached revision. This is untested as I don't have a linux box
to hand, but I believe it's right.
Ignore that - I managed
Andrew Dunstan wrote:
Here is my latest version of this patch. The good news is that it now
seems to work on Windows. Please review carefully (esp Magnus, Dave, Tom).
Hi Andrew,
I've eyeballed the code quite thoroughly and given it a whirl under
VC++. The only problem I found was that the
Gavin M. Roy wrote:
This is the patch I proposed on hackers to make pg_dump optionally
ignore tablespaces. The patch is against 8.2.4. If I should be
applying it to CVS head or what not, please let me know (along with any
thoughts, concerns or issues).
Hi Gavin,
It should be against -head
Michael Glaesemann wrote:
On Jul 7, 2007, at 13:50 , Tom Lane wrote:
Zdenek Kotala [EMAIL PROTECTED] writes:
Dave Page wrote:
This is almost as bad as Magnus agreeing with JD (!), but I agree with
Peter :-). After years of typing the current names, changing them does
seem somewhat
On Fri, July 6, 2007 8:51 am, Peter Eisentraut wrote:
Am Mittwoch, 4. Juli 2007 17:04 schrieb Zdenek Kotala:
I attach complete patch which renames following binaries
createdb createlang createuser dropdb droplang dropuser clusterdb
vacuumdb reindexdb
I just want to say I dislike this idea.
Andrew Dunstan wrote:
Further update attached. Includes some code cleanup, and now sets up a
session-id for all processes, including postmaster, syslogger etc, so we
can make a primary key on the log table of (session_id, line_number).
TODOs: fix on Windows, docs.
I'm not going to be able
The attached patch implements the following fixes to pg_ctl on Windows:
- Fix the -w (wait) option to work in Windows service mode, per bug
#3382. This is required on Windows because pg_ctl reports running status
to the service control manager when actually still in recovery/startup,
causing
Per previous discussion with Magnus, the attached batch file (rename to
install.bat) is a wrapper script for the MSVC installer. It sets up the
environment before installing (to allow zic.exe to run properly), and
removes the need to explicitly call perl on the command line.
This should be
The MSVC installer doesn't install the headers in the same directory
structure as the Mingw build. This causes other apps (such as Slony) to
fail their configure tests.
The attached patch fixes this.
Regards, Dave
Index: Install.pm
The attached patch installs libpgport.lib under MSVC, and corrects a
typo in a message.
Regards, Dave
Index: Install.pm
===
RCS file: /projects/cvsroot/pgsql/src/tools/msvc/Install.pm,v
retrieving revision 1.12
diff -c -r1.12
Magnus Hagander wrote:
On Wed, Apr 25, 2007 at 02:57:41PM +0100, Dave Page wrote:
The MSVC installer doesn't install the headers in the same directory
structure as the Mingw build. This causes other apps (such as Slony) to
fail their configure tests.
The attached patch fixes this.
Applied
Andrew Dunstan wrote:
Dave Page wrote:
Magnus Hagander wrote:
On Wed, Apr 25, 2007 at 02:57:41PM +0100, Dave Page wrote:
The MSVC installer doesn't install the headers in the same directory
structure as the Mingw build. This causes other apps (such as Slony)
to fail their configure tests
--- Original Message ---
From: Magnus Hagander [EMAIL PROTECTED]
To: Tom Lane [EMAIL PROTECTED]
Sent: 25/04/07, 22:31:20
Subject: Re: [PATCHES] Fix for MSVC header installation
Yup. I had no idea it did that :-) It certainly explains the difference.
No, nor I, but it makes sense
Bruce Momjian wrote:
Simon Riggs wrote:
I've sent through v10 of my patch for transaction guarantee = off twice
now and it hasn't shown up on-list. I don't appear to be blocked, so I'm
not sure what the problem is?
Sent: 31 Mar 22:09 TZ+01:00
Sent: 1 Apr 12:11 TZ+01:00
What an obvious
Bruce Momjian wrote:
Dave Page wrote:
Bruce Momjian wrote:
Simon Riggs wrote:
I've sent through v10 of my patch for transaction guarantee = off twice
now and it hasn't shown up on-list. I don't appear to be blocked, so I'm
not sure what the problem is?
Sent: 31 Mar 22:09 TZ+01:00
Sent: 1
Bruce Momjian wrote:
Thanks for the report. I have corrected this and the fix will be in
PostgreSQL 8.3. Interestingly, we support non-documented option
append and file too.
Append is undocumented as it's intended to be used by pg_dumpall, not
directly by users.
Regards, Dave.
Bruce Momjian wrote:
Dave Page wrote:
Bruce Momjian wrote:
Thanks for the report. I have corrected this and the fix will be in
PostgreSQL 8.3. Interestingly, we support non-documented option
append and file too.
Append is undocumented as it's intended to be used by pg_dumpall
Bruce Momjian wrote:
Peter Eisentraut wrote:
I was hoping that we're deprecating contrib/xml2, so I wouldn't add more
features to it.
Author states:
I understand that XML support is planned and at least partially
implemented for 8.3, but many production instances will be unable (or,
in
Bruce Momjian wrote:
Patch applied. Thanks.
Docs updated to mention Win32:
Write the output to the specified file. This is particularly useful
on Windows because output redirection does not work for child
processes.
I didn't say that - I said that I couldn't
Tom Lane wrote:
Dave Page [EMAIL PROTECTED] writes:
OK, updated patch attached. This has
-E dbname or --default-database=dbname
Not sure that default database is a particularly helpful adjective;
why shouldn't the switch just be --database?
Other than that, looks fine.
Updated to -l
Per discussion on -hackers, the attached patch adds the option
-f, --file=FILENAME
to pg_dumpall. In order to support this, a new (undocumented) format
option (-Fa) is added to pg_dump which is identical to -Fp, except that
the output file is opened for append rather than write.
This patch
Tom Lane wrote:
Dave Page [EMAIL PROTECTED] writes:
pg_dumpall -g -- Dump roles and tablespaces per current behaviour
pg_dumpall -gr -- Dump roles only (or users and groups)
pg_dumpall -gt -- Dump tablespaces only
This seems a bit ugly, mainly because (1) it doesn't have a natural
Per discussion on -hackers, the attached patch allow the default
database to be specified on the pg_dumpall command line, eg.
pg_dumpall [options...] [dbname]
If dbname is not specified, postgres/template1 are used per current
behaviour. If a connection cannot be made to dbname, an error is
Peter Eisentraut wrote:
Am Montag, 15. Januar 2007 14:44 schrieb Dave Page:
Per discussion on -hackers, the attached patch allow the default
database to be specified on the pg_dumpall command line, eg.
pg_dumpall [options...] [dbname]
I think this should be a separate option. Otherwise
Per discussion on -hackers, the attached patch introduces an optional
parameter to pg_dumpall's -g (--globals-only) option to allow roles or
tablespaces to be dumped on their own.
eg.
pg_dumpall -g -- Dump roles and tablespaces per current behaviour
pg_dumpall -gr -- Dump roles only (or users
Andrew Dunstan wrote:
Tom Lane wrote:
Dave Page [EMAIL PROTECTED] writes:
pg_dumpall -g -- Dump roles and tablespaces per current behaviour
pg_dumpall -gr -- Dump roles only (or users and groups)
pg_dumpall -gt -- Dump tablespaces only
This seems a bit ugly, mainly because (1
subscribe
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bruce Momjian
Sent: 26 October 2006 14:19
To: Albert Cervera Areny
Cc: pgsql-patches@postgresql.org
Subject: Re: [PATCHES] Tablespace for temporary objects and sort files
This has been saved
-Original Message-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]
Sent: 26 October 2006 14:37
To: [EMAIL PROTECTED]
Cc: Dave Page; Albert Cervera Areny; pgsql-patches@postgresql.org
Subject: Re: [PATCHES] Tablespace for temporary objects and sort files
bruce wrote:
Dave Page
The attached micropatch fixes the README install for contrib/sslinfo.
Regards, Dave.
sslinfo.diff
Description: sslinfo.diff
---(end of broadcast)---
TIP 6: explain analyze is your friend
-Original Message-
From: [EMAIL PROTECTED] on behalf of Jonah H. Harris
Sent: Sun 8/27/2006 3:24 AM
To: Joshua D. Drake
Cc: Andrew Dunstan; Bruce Momjian; Tzahi Fadida; pgsql-patches@postgresql.org
Subject: Re: [PATCHES] Adding fulldisjunctions to the contrib
It's odd, only 10 people
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: 21 August 2006 20:24
To: pgsql-hackers@postgresql.org; Magnus Hagander
Cc: Dave Page; pgsql-patches@postgresql.org
Subject: Re: [PATCHES] [HACKERS] BF Failure on Bandicoot
Magnus Hagander [EMAIL PROTECTED
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Andrus
Sent: 08 May 2006 18:16
To: pgadmin-hackers@postgresql.org
Subject: Re: [pgadmin-hackers] Adminpack contrib module
There were no objections, so attached is an updated version of the
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Marko Kreen
Sent: 05 May 2006 12:22
To: Tom Lane
Cc: Martijn van Oosterhout; pgsql-patches@postgresql.org
Subject: Re: [PATCHES] [PATCH] Have configure complain about
unknown options
As
A few weeks ago following a discussion on pgsql-general it was proposed that
the pgAdmin 'adminpack' contrib module be added to /contrib in the server's
source tree to make it easier for users to find and install.
There were no objections, so attached is an updated version of the
adminpack, with
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane
Sent: 24 April 2006 21:57
To: Magnus Hagander
Cc: Chuck McDevitt; pgsql-patches@postgresql.org
Subject: Re: [PATCHES] Building with Visual C++
We'll need a VC buildfarm member in place
xml2.patch The attached patch fixes the xml2 contrib module for
windows, by changing the order of -lxslt -lxml2 (yes, after 2 releases
that's all it took!). Tested on Windows Linux.
It might be worth manually testing this on any other platforms that
might be sensitive to the library order -
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Peter Eisentraut
Sent: 06 January 2006 11:07
To: pgsql-patches@postgresql.org
Cc: Hiroshi Saito
Subject: Re: [PATCHES] display and expression of the home
directory in Win32
Am Freitag, 6.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane
Sent: 09 December 2005 14:01
To: Hiroshi Saito
Cc: Magnus Hagander; Bruce Momjian; PostgreSQL-patches
Subject: Re: [PATCHES] CVS of 8.1.x MS-VC6 probrem.
Hiroshi Saito [EMAIL
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: 09 December 2005 14:33
To: Dave Page
Cc: Hiroshi Saito; Magnus Hagander; Bruce Momjian; PostgreSQL-patches
Subject: Re: [PATCHES] CVS of 8.1.x MS-VC6 probrem.
Dave Page dpage@vale-housing.co.uk writes:
As one
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Joshua D. Drake
Sent: 17 November 2005 15:58
To: Andreas Pflug
Cc: Tom Lane; Simon Riggs; pgsql-patches@postgresql.org
Subject: Re: [PATCHES] Numeric 508 datatype
Hm, so if this patch is
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Michael Glaesemann
Sent: 14 November 2005 14:54
To: Andrew Dunstan
Cc: Patches (PostgreSQL)
Subject: Re: [PATCHES] drop if exists
On Nov 14, 2005, at 23:25 , Andrew Dunstan wrote:
Ther
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: 05 October 2005 16:31
To: Dave Page
Cc: Bruce Momjian; PostgreSQL-patches
Subject: Re: [PATCHES] Fix for file names with spaces
Dave Page dpage@vale-housing.co.uk writes:
Why does this patch convert
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: 05 October 2005 16:08
To: Bruce Momjian
Cc: PostgreSQL-patches; Dave Page
Subject: Re: [PATCHES] Fix for file names with spaces
Bruce Momjian pgman@candle.pha.pa.us writes:
Sorry, this is the same patch
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane
Sent: 03 October 2005 15:37
To: Simon Riggs
Cc: pgsql-hackers@postgresql.org; pgsql-patches@postgresql.org
Subject: Re: [PATCHES] [HACKERS] External Sort timing debug
statements
builds work with a relocated installation
Dave Page dpage@vale-housing.co.uk writes:
Unfortunately quoting either way didn't work on Windows/msys when
Thomas I were looking at this.
Yech. So we need the GetShortName hack on Windows even if we quote
for other platforms?
Yep :-(.
/D
-Original Message-
From: Tom Lane[EMAIL PROTECTED]
Sent: 01/10/05 16:28:18
To: Bruce Momjianpgman@candle.pha.pa.us
Cc: Dave Pagedpage@vale-housing.co.uk, Peter Eisentraut[EMAIL
PROTECTED], PostgreSQL-patchespgsql-patches@postgresql.org
Subject: Re: Making pgxs builds work with a
The attached patch fixes a couple of minor issues in the file access
functions added for 8.1. These seem to have been introduced in recent
changes following the original patch.
1) Stop them rejecting paths that use Windows backslash directory
seperators.
2) Allow absolute paths to files into the
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: 29 August 2005 20:15
To: Dave Page
Cc: PostgreSQL-patches
Subject: Re: [PATCHES] Bug in file access functions
Dave Page dpage@vale-housing.co.uk writes:
1) Stop them rejecting paths that use Windows backslash
It, or some related patch appears to have broken the build on buildfarm member
snake.
I haven't had time to investigate.
/D
-Original Message-
From: Bruce Momjianpgman@candle.pha.pa.us
Sent: 25/08/05 01:14:54
To: Tom Lane[EMAIL PROTECTED]
Cc: Andrew Dunstan[EMAIL PROTECTED], Chuck
-Original Message-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]
Sent: 01 August 2005 03:26
To: Dave Page
Cc: PostgreSQL-patches
Subject: Re: [HACKERS] For review: Server instrumentation patch
Dave Page wrote:
[Resent as the list seems to have rejected yesterdays attempt
The attached patch updates the thread test program to run stand-alone on
Windows. The test itself is bypassed in configure as discussed, and
libpq has been updated appropriately to allow it to build in thread-safe
mode.
To apply, apply the patch as normal, then rename
-Original Message-
From: Andreas Pflug [mailto:[EMAIL PROTECTED]
Sent: 01 August 2005 14:47
To: Dave Page
Cc: Bruce Momjian; PostgreSQL-patches
Subject: Re: [PATCHES] [HACKERS] For review: Server
instrumentation patch
Dave Page wrote:
-Original Message
-Original Message-
From: Andreas Pflug [mailto:[EMAIL PROTECTED]
Sent: 01 August 2005 15:05
To: Dave Page
Cc: Bruce Momjian; PostgreSQL-patches
Subject: Re: [PATCHES] [HACKERS] For review: Server
instrumentation patch
Dave Page wrote:
pg_dir_ls isn't necessary
-Original Message-
From: [EMAIL PROTECTED] on behalf of Tom Lane
Sent: Sat 7/30/2005 4:58 PM
To: Magnus Hagander
Cc: PostgreSQL-patches
Subject: Re: [PATCHES] Updated instrumentation patch
None of these functions are getting into 8.1 anyway; we should be
designing the long-term
-Original Message-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]
Sent: 06 July 2005 04:11
To: Tom Lane
Cc: Dave Page; Christopher Kings-Lynne; Robert Treat; Dawid
Kuroczko; Andreas Pflug; PostgreSQL-patches; PostgreSQL-development
Subject: Re: [HACKERS] [PATCHES] Dbsize backend
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: 03 July 2005 17:10
To: Dawid Kuroczko
Cc: Andreas Pflug; Dave Page; Bruce Momjian;
PostgreSQL-patches; PostgreSQL-development
Subject: Re: [HACKERS] [PATCHES] Dbsize backend integration
Dawid Kuroczko [EMAIL
-Original Message-
From: Robert Treat [mailto:[EMAIL PROTECTED]
Sent: 04 July 2005 18:21
To: Dave Page
Cc: Tom Lane; Dawid Kuroczko; Andreas Pflug; Bruce Momjian;
PostgreSQL-patches; PostgreSQL-development
Subject: Re: [HACKERS] [PATCHES] Dbsize backend integration
-Original Message-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]
Sent: 02 July 2005 21:30
To: Bruce Momjian
Cc: Dave Page; PostgreSQL-patches; PostgreSQL-development
Subject: Re: [PATCHES] Dbsize backend integration
Is a new version of this patch coming?
Yup, attached. Per
-Original Message-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]
Sent: 29 June 2005 12:46
To: Dave Page
Cc: PostgreSQL-patches; PostgreSQL-development
Subject: Re: [PATCHES] Dbsize backend integration
I have a new idea --- pg_storage_size().
I'm not against that one, but I
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 30 June 2005 10:29
To: Bruce Momjian; Dave Page
Cc: PostgreSQL-patches; PostgreSQL-development
Subject: Re: [PATCHES] Dbsize backend integration
Maybe pg_trait_size() or pg_property_size() will do?
I
1 - 100 of 175 matches
Mail list logo
