> -Original Message-
> From: Andrew Dunstan [mailto:[EMAIL PROTECTED]
> Sent: 26 August 2004 15:43
> To: Dave Page
> Cc: Magnus Hagander; Tom Lane;
> [EMAIL PROTECTED]; PostgreSQL-patches
> Subject: Re: [PATCHES] [pgsql-hackers-win32] postmaster.pid
>
>
&
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: 26 August 2004 16:24
> To: Dave Page
> Cc: Andrew Dunstan; Magnus Hagander;
> [EMAIL PROTECTED]; PostgreSQL-patches
> Subject: Re: [PATCHES] [pgsql-hackers-win32] postmaster.pid
>
> &q
Hi,
The attached patch addresses the following issues with the WIn32 service
code in pg_autovacuum. Please apply.
- Add documentation.
- Use the main PostgreSQL message dll when logging to the application
log.
- Set the -P (port) option correctly when installing as a service.
Regards, Dave
pg_
Evening committers,
Any ideas when Magnus' win32 version numbering patch is likely to get
applied?
Regards, Dave.
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes d
> -Original Message-
> From: Magnus Hagander [mailto:[EMAIL PROTECTED]
> Sent: 02 September 2004 09:47
> To: Bruce Momjian; Dave Page
> Cc: PostgreSQL-patches
> Subject: RE: [PATCHES] Win32 Version patch
>
> But I can send
> the same patch again.
The Win32 installer cannot easily handle 'copy from stdin' thus
preventing execution of scripts that use copy. Tsearch2 appears to have
the only script that does this - the attached patch changes the copy to
a bunch of INSERTs.
Regards, Dave
tsearch2.sql.in.diff
Description: tsearch2.sql.in.diff
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: 08 September 2004 15:14
> To: Dave Page
> Cc: PostgreSQL-patches
> Subject: Re: [PATCHES] Tsearch2 update for Win32.
>
> While I have no particular objection to adjusting the
> t
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: 08 September 2004 15:49
> To: Magnus Hagander
> Cc: Dave Page; PostgreSQL-patches
> Subject: Re: [PATCHES] Tsearch2 update for Win32.
>
> I was about to mention trapping errors as being
> -Original Message-
> From: Andrew Dunstan [mailto:[EMAIL PROTECTED]
> Sent: 08 September 2004 17:17
> To: Tom Lane
> Cc: Magnus Hagander; Dave Page; PostgreSQL-patches
> Subject: Re: [PATCHES] Tsearch2 update for Win32.
>
>
> Not to mention someone
> -Original Message-
> From: Andreas Pflug [mailto:[EMAIL PROTECTED]
> Sent: 08 September 2004 19:15
> To: Dave Page
> Cc: PgSQL Win32 developers; PostgreSQL Patches
> Subject: Re: [pgsql-hackers-win32] Contrib modules on Win32
>
> Dave Page wrote:
> >
> -Original Message-
> From: Bruce Momjian [mailto:[EMAIL PROTECTED]
> Sent: 10 September 2004 17:41
> To: [EMAIL PROTECTED]
> Cc: Dave Page; PgSQL Win32 developers
> Subject: Re: [pgsql-hackers-win32] VC++ psql build broken
>
>
> Now that I think of it,
> -Original Message-
> From: Bruce Momjian [mailto:[EMAIL PROTECTED]
> Sent: 12 September 2004 14:59
> To: Dave Page
> Cc: PgSQL Win32 developers; PostgreSQL Patches
> Subject: Re: [pgsql-hackers-win32] VC++ psql build broken
>
>
> How does your Win32 sys
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: 14 September 2004 05:00
> To: Dave Page
> Cc: PostgreSQL-patches
> Subject: Re: [PATCHES] Tsearch2 update for Win32.
>
> "Dave Page" <[EMAIL PROTECTED]> writes:
> >
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Barry Lind
> Sent: 21 September 2004 00:46
> To: [EMAIL PROTECTED]
> Subject: [pgsql-hackers-win32] pg_autovacuum log paths can't
> contain spaces
>
> I just installed the beta2 Dev 3 version of
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Magnus Hagander
> Sent: 11 October 2004 21:05
> To: pgsql-patches
> Subject: [PATCHES] libpq.dll on win32
>
> * Adds required functions to libpqdll.def and libpqddll.def.
> This includes the fun
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane
> Sent: 12 October 2004 01:38
> To: Magnus Hagander
> Cc: pgsql-patches
> Subject: Re: [PATCHES] libpq.dll on win32
>
> Also, I count 3 *.def files to be fixed, not two. (We really
> oug
> -Original Message-
> From: Bruce Momjian [mailto:[EMAIL PROTECTED]
> Sent: 12 October 2004 02:08
> To: Dave Page
> Cc: [EMAIL PROTECTED]; PostgreSQL-patches
> Subject: Re: [pgsql-hackers-win32] Static build of libpq fails
>
> Dave Page wrote:
> > H
> -Original Message-
> From: Bruce Momjian [mailto:[EMAIL PROTECTED]
> Sent: 13 October 2004 10:52
> To: Dave Page
> Cc: [EMAIL PROTECTED]; PostgreSQL-patches;
> PostgreSQL Cygwin mailing list
> Subject: Re: [pgsql-hackers-win32] Static build of libpq fails
> -Original Message-
> From: Bruce Momjian [mailto:[EMAIL PROTECTED]
> Sent: 27 September 2004 23:58
> To: Dave Page
> Cc: PgSQL Win32 developers; PostgreSQL Patches
> Subject: Re: [pgsql-hackers-win32] VC++ psql build broken
>
>
> I have fixed this issue
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Dave Page
> Sent: 28 September 2004 12:06
> To: Bruce Momjian
> Cc: PgSQL Win32 developers; PostgreSQL Patches
> Subject: Re: [pgsql-hackers-win32] VC++ psql build broke
> -Original Message-
> From: Magnus Hagander [mailto:[EMAIL PROTECTED]
> Sent: 30 September 2004 23:00
> To: PostgreSQL-patches
> Cc: Dave Page
> Subject: SSL on win32
>
> Hello!
>
> Here is a patch to fix win32 ssl builds. Summary of changes:
>
>
The patch below removes attempts to drop objects before creating them
from the int_aggregate and pgstattuple SQL scripts. This causes the
script to fail on databases where the affected objects don't already
exist when the script is executed by the Win32 installer, pgAdmin or any
other interface tha
Tom's recent patch to improve stale lockfile detection included a call
to getppid() which doesn't exist on Windows. There is no clean way to
implement one (previously discussed on hackers-win32) hence the attach
patch simply #ifdefs out the call.
Please apply ASAP as the win32 build is currently b
More haste, less speed...
Patch attached this time!
/D
> -Original Message-
> From: Dave Page
> Sent: 04 October 2004 14:41
> To: PostgreSQL-patches
> Subject: Win32 fix for miscinit.c
>
> Tom's recent patch to improve stale lockfile detection
> inclu
The Win32 (mingw) build of libpq seems to have lost it's SSL libs from
the link step resulting in a build failure. The attached patch fixes
that.
Please apply asap.
Thanks, Dave
libpq_ssl.patch
Description: libpq_ssl.patch
---(end of broadcast)--
Unfortunately some re-jigging of Magnus' Win32 version patch broke the
build by introducing some un-escaped double quotes into sed commands.
The attached patch escapes those quotes without removing the re-jigging
that was done.
Regards, Dave.
filedesc.diff
Description: filedesc.diff
---
> -Original Message-
> From: Magnus Hagander [mailto:[EMAIL PROTECTED]
> Sent: 06 October 2004 15:27
> To: Dave Page; PostgreSQL-patches
> Subject: RE: [PATCHES] Win32 VERSIONINFO fix
>
>
> > Unfortunately some re-jigging of Magnus' Win32 version
Not entirely sure when this broke, but libpq's VC++ build is currently
lacking pqsignal which is now required. This was found and fixed for
VC++ by Shachar Shemesh, I simply duplicated the fix for the Borland
makefile (untested, as I don't have that compiler).
Please apply.
Regards, Dave
pqsign
The attached patch fixes psql's win32 frontend-only build, by using
pg_strcasecmp in variables.c, and #ifdef'ing out PostmasterPid in
miscadmin.h.
Please apply.
Regards Dave.
psql.diff
Description: psql.diff
---(end of broadcast)---
TIP 9: the pl
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: 18 October 2004 18:37
> To: Dave Page
> Cc: PostgreSQL-patches
> Subject: Re: [PATCHES] Win32 psql fix
>
> "Dave Page" <[EMAIL PROTECTED]> writes:
> > The attached pa
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Matthew T. O'Connor
> Sent: 26 October 2004 06:40
> To: pgsql-patches
> Subject: [PATCHES] pg_autovacuum vacuum cost variables patch
>
> Please review and if deemed accecptable, please apply to
-Original Message-
From: [EMAIL PROTECTED] on behalf of Tom Lane
Sent: Sat 11/6/2004 5:30 AM
To: Bruce Momjian
Cc: PostgreSQL-patches
Subject: Re: [PATCHES] psql \! WIN32 cleanup
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> The attached applied patch tests for COMSPEC in the right pla
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Bruce Momjian
> Sent: 27 November 2004 04:33
> To: [EMAIL PROTECTED]
> Cc: PostgreSQL Win32 port list; PostgreSQL-development
> Subject: Re: [pgsql-hackers-win32] [BUGS] pg_autovacuum in
> 8beta-
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Neil Conway
> Sent: 12 December 2004 22:57
> To: pgsql-patches
> Subject: [PATCHES] pg_resetxlog as root
>
> I suppose a similar fix is needed for Win32? If so,
> pgwin32_is_admin() would be the na
> -Original Message-
> From: Neil Conway [mailto:[EMAIL PROTECTED]
> Sent: 13 December 2004 03:59
> To: Dave Page
> Cc: pgsql-patches
> Subject: RE: [PATCHES] pg_resetxlog as root
>
> On Sun, 2004-12-12 at 23:59 +, Dave Page wrote:
> > Sounds reason
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Bruce Momjian
> Sent: 07 January 2005 05:33
> To: Andrew Dunstan
> Cc: Patches (PostgreSQL)
> Subject: Re: [PATCHES] pg_config MSVC makefile
>
>
> This has been saved for the 8.1 release:
>
>
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tony and Bryn
ReinaSent: 07 January 2005 10:57To:
pgsql-patches@postgresql.orgSubject: Re: [PATCHES] pg_config MSVC
makefile
> Dave Page wrote:
> Err, I missed this earlier - we had
dis
> -Original Message-
> From: Bruce Momjian [mailto:[EMAIL PROTECTED]
> Sent: 07 January 2005 15:14
> To: Dave Page
> Cc: Andrew Dunstan; Patches (PostgreSQL)
> Subject: Re: [PATCHES] pg_config MSVC makefile
>
> I am not in favor of removing those makefiles in 8
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: 07 January 2005 16:25
> To: Bruce Momjian
> Cc: Dave Page; Andrew Dunstan; Patches (PostgreSQL)
> Subject: Re: [PATCHES] pg_config MSVC makefile
>
>
> > more of a pain. If people a
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: 07 January 2005 17:07
> To: Dave Page
> Cc: Bruce Momjian; Andrew Dunstan; Patches (PostgreSQL)
> Subject: Re: [PATCHES] pg_config MSVC makefile
>
> Don't feel that it's on yo
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Harald Massa
> Sent: 20 January 2005 13:30
> To: [EMAIL PROTECTED]
> Subject: [pgsql-hackers-win32] pg_autovacuum fails to start -
> 8.0 Release
>
> I am trying to install pg_autovacuum as a win
> -Original Message-
> From: Harald Massa [mailto:[EMAIL PROTECTED]
> Sent: 20 January 2005 16:07
> To: Dave Page
> Cc: [EMAIL PROTECTED]; pgsql-patches@postgresql.org
> Subject: RE: [pgsql-hackers-win32] pg_autovacuum fails to
> start - 8.0 Release
>
> Dav
> -Original Message-
> From: Harald Massa [mailto:[EMAIL PROTECTED]
> Sent: 20 January 2005 16:17
> To: Dave Page
> Cc: [EMAIL PROTECTED]; pgsql-patches@postgresql.org
> Subject: RE: [pgsql-hackers-win32] pg_autovacuum fails to
> start - 8.0 Release
>
> Dav
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Dave Page
> Sent: 20 January 2005 15:29
> To: Harald Massa; [EMAIL PROTECTED]
> Cc: Patches (PostgreSQL)
> Subject: Re: [PATCHES] [pgsql-hackers-win32] pg_autovacuum
> fail
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Dave Page
> Sent: 21 January 2005 13:20
> To: Harald Massa; [EMAIL PROTECTED]
> Subject: Re: [pgsql-hackers-win32] 300 seconds in less than 1
> s
> -Original Message-
> From: Andrew Dunstan [mailto:[EMAIL PROTECTED]
> Sent: 21 January 2005 14:01
> To: Dave Page
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
> pgsql-patches@postgresql.org
> Subject: Re: [PATCHES] [pgsql-hackers-win32] 300 seconds in
>
Theis patch supercedes *all* my earlier ones from today - apologies for
the noise, clearly I need a beer or 3 and a few nights away from the
laptop.
The following fixes are included:
- Dependency services may not be correctly registered when installing as
a Windows Service.
- The sleep time is
> -Original Message-
> From: Neil Conway [mailto:[EMAIL PROTECTED]
> Sent: 22 January 2005 10:13
> To: Dave Page
> Cc: pgsql-patches@postgresql.org
> Subject: Re: [PATCHES] pg_autovacuum/Win32 Fixes
>
> Dave Page wrote:
> > Theis patch supercedes *a
When starting as a service at boot time on Windows, pg_autovacuum may
fail to start because the PostgreSQL service is still starting up. This
patch causes the service to attempt a second connection 30 seconds after
the initial connection failure before giving up entirely.
Regards, Dave
startup_d
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: 24 January 2005 23:58
> To: Dave Page
> Cc: pgsql-patches@postgresql.org
> Subject: Re: [PATCHES] pg_autovacuum Win32 Service startup delay
>
> "Dave Page" writes:
> > Wh
Add missing quotes.
Index: docguide.sgml
===
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/docguide.sgml,v
retrieving revision 1.55
diff -u -r1.55 docguide.sgml
--- docguide.sgml 9 Apr 2005 03:52:43 - 1.55
+++ docgui
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane
> Sent: 24 May 2005 15:17
> To: Ian FREISLICH
> Cc: pgsql-patches@postgresql.org
> Subject: Re: [PATCHES] [PATCH] pg_autovacuum commandline
> password hiding.
>
> Ian FREISLICH <[EMAIL PR
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: 24 May 2005 16:02
> To: Dave Page
> Cc: Ian FREISLICH; pgsql-patches@postgresql.org
> Subject: Re: [PATCHES] [PATCH] pg_autovacuum commandline
> password hiding.
>
> "Dave Page
> -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()
> >
The attached patch modifies initdb to create a default database called
'postgres' when the cluster is initialised. Documentation updates are
included, including updates to relevant examples to encourage users to
use this database in place of template1. I have not modified utilities
like createuser
Attached is an updated version of this patch which /does/ update
utilities to use the postgres database by default, per comments on
-hackers.
Regards, Dave
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Dave Page
> Sent: 20 June 200
The attached patch integrates dbsize functions into the backend, as per
discussion on -hackers. The following functions are included:
pg_relation_size(text) - Get relation size by name/schema.name
pg_relation_size(oid)- Get relation size by OID
pg_tablespace_size(name) - Get tablespace size
-Original Message-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]
Sent: Wed 6/29/2005 2:16 AM
To: Dave Page
Cc: PostgreSQL-patches; PostgreSQL-development
Subject: Re: [PATCHES] Dbsize backend integration
> OK, so you went with relation as heap/index/toast only, and table as
> -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().
> -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
> -Original Message-
> From: Michael Glaesemann [mailto:[EMAIL PROTECTED]
> Sent: 30 June 2005 10:01
> To: Dave Page
> Cc: PostgreSQL-patches; PostgreSQL-development
> Subject: Re: [PATCHES] Dbsize backend integration
>
>
> I'm still unclear as
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: 30 June 2005 14:41
> To: Dave Page
> Cc: Michael Glaesemann; PostgreSQL-patches; PostgreSQL-development
> Subject: Re: [PATCHES] Dbsize backend integration
>
> "Dave Page" wri
> -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
> -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 in
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: 04 July 2005 14:54
> To: Dave Page
> Cc: Dawid Kuroczko; Andreas Pflug; Bruce Momjian;
> PostgreSQL-patches; PostgreSQL-development
> Subject: Re: [HACKERS] [PATCHES] Dbsize backend integra
> -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] Dbsiz
> -Original Message-
> From: Christopher Kings-Lynne [mailto:[EMAIL PROTECTED]
> Sent: 05 July 2005 02:39
> To: Robert Treat
> Cc: Bruce Momjian; Dave Page; Tom Lane; Dawid Kuroczko;
> Andreas Pflug; PostgreSQL-patches; PostgreSQL-development
> Subject: Re: [HACK
> -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: [HACK
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 cli
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
alrea
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
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'
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 a
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
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 th
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 acce
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
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 figu
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,
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, bu
> --- 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 pat
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
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 her
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, "
A discussion on -general has been ongoing in which is was discovered
that 8.3 can exhaust the desktop heap allocated to a service with ~45
connections at which point the server will crash.
Desktop heap is allocated by user32.dll and shell32 on a per-process
basis from a 512KB pool for a non-intera
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()
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: /projects/cv
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 = gete
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
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 it
Neil Conway wrote:
> On Mon, 2007-12-10 at 19:27 +0000, 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
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 PGO
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
Andrew Dunstan wrote:
> Writing and calling a temp .bat file might be yucky - having to keep two
> environment files is a lot more yucky, IMNSHO, and we shouldn't make
> people do it.
+1
/D
---(end of broadcast)---
TIP 9: In versions below 8.0, the
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 ex
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. E
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 p
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.
sume the child 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 Pa
101 - 200 of 210 matches
Mail list logo
