[PATCHES] SSL configure patch

2008-06-13 Thread pgsql
Here is the SSL patch we discussed previously for 8.3.1. sslconfig.patch.8.3.1 Description: Binary data -- Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-patches

[PATCHES] SSL client configuration patch

2008-05-15 Thread pgsql
beros service name */ #endif diff -u -r postgresql-8.2.7/src/interfaces/libpq/libpq.rc postgresql-8.2.7-ssl/src/interfaces/libpq/libpq.rc --- postgresql-8.2.7/src/interfaces/libpq/libpq.rc 2008-03-14 22:52:42.0 -0400 +++ postgresql-8.2.7-ssl/src/interfaces/libpq/libpq.rc 2008-05-15 14:51:41.529453351 -0400 @@ -1,8 +1,8 @@ #include VS_VERSION_INFO VERSIONINFO - FILEVERSION 8,2,7,8074 - PRODUCTVERSION 8,2,7,8074 + FILEVERSION 8,2,7,8136 + PRODUCTVERSION 8,2,7,8136 FILEFLAGSMASK 0x3fL FILEFLAGS 0 FILEOS VOS__WINDOWS32 -- Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-patches

[PATCHES] Contrib Shared varaibles

2004-08-26 Thread pgsql
After taking some suggestions, I added a number of routines. Please test and tell me what you think. (Yes, I know the API is poorly named, have any suggestions?) sharedvar-040826.tgz Description: application/unix-tar ---(end of broadcast)--- TIP

Re: [PATCHES] Contrib -- PostgreSQL shared variables -with swap

2004-08-25 Thread pgsql
This new version contains, in addition to the previous version, SwapShared(..) which allows you to swap a value in a variable. sharedvar-040825.tgz Description: application/unix-tar ---(end of broadcast)--- TIP 7: don't forget to increase your free

Re: [PATCHES] [HACKERS] Contrib -- PostgreSQL shared variables

2004-08-25 Thread pgsql
> LockShared('name'); Hmmm, I thought about that, but it is *WAY* more complicated than it looks. What if after a "Lock" the process crashes before it can call "Unlock?" It is this problem that inspired the "add" and "sub" calls. > > [EMAIL PROTECTED] wrote: >> This is a first pass on a simple

[PATCHES] Contrib -- PostgreSQL shared variables

2004-08-25 Thread pgsql
This is a first pass on a simple shared memory variable system for PostgreSQL. I would appriciate anyone interested in this functionality to rip it apart. It basically adds this functionality: SetShared('name', value); GetSharedInt('name'); SetSharedText('name); RemovedShared('name'); I also add

Re: [PATCHES] [HACKERS] Configuration patch

2004-06-03 Thread pgsql
> [EMAIL PROTECTED] writes: >>> AFAICS this patch breaks standalone backends, since the smarts involved >>> in dealing with the new flavors of directory layouts were not taught to >>> postgres.c. > >> Hmm, I guess its time to get a CVS version of PG. This was originally >> done >> in 7.3 and migrat

Re: [PATCHES] [HACKERS] Configuration patch

2004-06-03 Thread pgsql
> Bruce Momjian <[EMAIL PROTECTED]> writes: >>> This patch incorporates a number of changes suggested by the group. The >>> purpose of this patch is to move postgresql to a position where all >>> configuration options are specified in one place. The postgresql.conf >>> file >>> could completely doc

Re: [PATCHES] [HACKERS] Configuration patch

2004-05-27 Thread pgsql
> > I am working on integrating this patch now. > > What is the logic if checkConfigDir(). It seems incompleted or wrong. > > Your code had: > > + if(S_ISREG(stat_buf.st_mode)) /* It's a regular file, so > assume it's an explict */ > + { > + return TRUE; > +

[PATCHES] Configuration patch

2004-05-12 Thread pgsql
This patch incorporates a number of changes suggested by the group. The purpose of this patch is to move postgresql to a position where all configuration options are specified in one place. The postgresql.conf file could completely document a postgresql environment. It adds this functionality: T