:
Chris Marcellino [EMAIL PROTECTED]
was not CC'ed as part of this email thread. That was a mistake.
Chris,
the email thread discussing your patch is here:
http://archives.postgresql.org/pgsql-hackers/2008-03/
msg01262.php
Please read the discussion --- the bottom line is that there isn't
be reached on
some platforms if a ton of databases are opened simultaneously (i.e.
256 on Linux and Solaris, 100 on SCO Unix, 512 on HP-UX, 32 on Mac OS
X, unlimited on FreeBSD). This is the case without the patch anyhow.
Chris Marcellino
On Mar 3, 2007, at 9:09 AM, Joshua D. Drake wrote
-0800, Chris Marcellino wrote:
So I've finished reformulating this patch to use the device/inode
instead of the hash idea I had earlier.
I have tested this patch (on Darwin) to permit the postmaster to
recover after a crash or killing, and it will not permit the
postmaster to restart while another
.
This might make it easier to avoid the complexity of fitting the
filename in the segment name, and avoid the rename problem,
Thanks,
Chris Marcellino
On Feb 27, 2007, at 12:56 AM, Magnus Hagander wrote:
On Mon, Feb 26, 2007 at 09:00:09PM -0800, Chris Marcellino wrote:
There is also a Windows
,
Chris Marcellino
On Feb 27, 2007, at 1:40 AM, Magnus Hagander wrote:
On Tue, Feb 27, 2007 at 10:30:15AM +0100, Magnus Hagander wrote:
Does Windows have a method to get a unique ID number for a given
data
directory, or a token file in that directory? It would need to be
constant while
-in the
desired patches. An autoconf'ing of the patched configure.in file is,
of course, required.
I appreciate the feedback and consideration.
Thanks again,
Chris Marcellino
win32.patch
Description: Binary data
configure.in.patch
Description: Binary data
netbsd.patch
Description: Binary data
being silently
dropped when I attached this large of a file):
http://homepage.mac.com/cmarcellino/postgres-posix-shmem.tar
Please let me know if there is a better way to post this.
Thanks for your feedback,
Chris Marcellino
---(end of broadcast
On Feb 26, 2007, at 10:43 PM, Tom Lane wrote:
Chris Marcellino [EMAIL PROTECTED] writes:
The System V shared memory facilities provide a method to determine
who is attached to a shared memory segment.
This is used to prevent backends that were orphaned by crashed or
killed database processes
settings (SHMMAX, etc.) can be
set to their default values to recover the memory that was wired down
for the SysV pool.
I don't have access to any Linux machines to test this.
Thanks for your feedback,
Chris Marcellino
posix_shmem.c
Description: Binary data
---(end
! ;;
! *)
! USE_SYSV_SEMAPHORES=1
! ;;
! esac
Thanks,
Chris Marcellino
darwin
Description: Binary data
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
, is that the SysV semaphores use less memory (and no
fd's). Darwin can support about 85k SysV semaphores system-wide, so
it has no need for tuning in that respect, which is nice.
Chris Marcellino
On Feb 7, 2007, at 4:54 PM, Tom Lane wrote:
Chris Marcellino [EMAIL PROTECTED] writes:
I searched through
? Suggestions? I would also appreciate any advice on more
sophisticate ways to measure the performance impacts of a change like
this.
Thanks,
Chris Marcellino
Apple Computer, Inc.
posix_shmem.c
Description: Binary data
src/backend/port/posix_shmem.c
, that is an interesting idea. That might be an avenue to
explore if there isn't a simpler way.
Thanks,
Chris Marcellino
On Feb 6, 2007, at 7:51 AM, Michael Paesold wrote:
Tom Lane wrote:
Chris Marcellino [EMAIL PROTECTED] writes:
To this end, I have ported the svsv_shmem.c layer to use the
POSIX
for confirming the existence of the other backend process.
Chris Marcellino
On Feb 6, 2007, at 10:32 AM, Alvaro Herrera wrote:
Chris Marcellino wrote:
Tom, that is a definitely valid point and thanks for the feedback. I
assume that the 'more modern' string segment naming gave the POSIX
methods
Responses inline.
On Feb 6, 2007, at 7:05 PM, Takayuki Tsunakawa wrote:
From: Chris Marcellino [EMAIL PROTECTED]
To this end, I have ported the svsv_shmem.c layer to use the POSIX
calls (which are some ways more robust w.r.t reducing collision by
using strings as shared memory id's, instead
Yes, as Tom pointed out. Sorry, I misread the autoconf file. I've
gotten quite used to Darwin == BSD.
I've added a note to my todo list to look into the posix semaphore
performance on the Darwin side.
--Chris
On Feb 6, 2007, at 8:32 PM, Takayuki Tsunakawa wrote:
Then, how about
? Do you think this
might be worth me trying?
Thanks for your help,
Chris Marcellino
posix_shmem.c
Description: Binary data
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
17 matches
Mail list logo
