Fwd: Hast + ZFS + Postgresql on FreeBSD 8.1
-- Forwarded message -- From: Omer Faruk SEN omerf...@gmail.com Date: Fri, Aug 20, 2010 at 10:57 PM Subject: Hast + ZFS + Postgresql on FreeBSD 8.1 To: FreeBSD freebsd-questions@freebsd.org Hi, Is there any one here in this list tried this combo on FreeBSD 8.1 ? I really would like to know your opinions about that. Especially I am concerned on how to keep consistency of database and recovery procedures in the event of failure (I mean pgsql recovery or any) Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Hast + ZFS + Postgresql on FreeBSD 8.1
Hi, Is there any one here in this list tried this combo on FreeBSD 8.1 ? I really would like to know your opinions about that. Especially I am concerned on how to keep consistency of database and recovery procedures in the event of failure (I mean pgsql recovery or any) Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: PostgreSQL on FreeBSD 7.0 amd64 with more than 2GB shared memory
Hell, Robert wrote: I just found a bug report for that issue: http://www.freebsd.org/cgi/query-pr.cgi?pr=121423cat= Try asking on current@ - I think there were some patches available some time ago. -Original Message- From: Wojciech Puchar [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 10. Dezember 2008 18:30 To: Hell, Robert Cc: freebsd-questions@freebsd.org Subject: Re: PostgreSQL on FreeBSD 7.0 amd64 with more than 2GB shared memory fails again with ENOMEM. Is there any easy way to use a shared memory segment which is larger than 2GB? getting two smaller ? :) no idea - maybe it's bug of SHM. as you already checked it please do sent-pr ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] signature.asc Description: OpenPGP digital signature
PostgreSQL on FreeBSD 7.0 amd64 with more than 2GB shared memory
Hi,
I'm trying to run PostgreSQL 8.3 on a FreeBSD 7.0 amd64 server with more
than 2GB shared memory. The machine has 32GB RAM installed.
After setting kern.ipc.shmmax and kern.ipc.shmall to the appropriate
values, I still had no chance to start postgres with more than 2GB of
shared memory.
I wrote a small test which does the same as postgres: shmget and shmat:
#include sys/ipc.h
#include sys/shm.h
#include stdio.h
#include errno.h
int main()
{
int shmid, memKey = 1;
void *memAddress;
unsigned long size = 2147483648UL;
shmid = shmget(memKey, size, IPC_CREAT | IPC_EXCL);
if (shmid 0) {
printf(shmget failed: %d\n, errno);
return 1;
}
memAddress = shmat(shmid, NULL, 0);
if (memAddress == (void *) -1) {
printf(shmat failed: %d\n, errno);
}
return 0;
}
I found out that shmget failed with ENOMEM in shmget_allocate_segment
(sysv_shm.c) because of an overflow of size (requested shared memory in
bytes):
int i, segnum, shmid, size;
...
size = round_page(uap-size);
if (shm_committed + btoc(size) shminfo.shmall) {
return (ENOMEM);
}
When changing size to an unsigned long shmget works - but now shmat then
fails again with ENOMEM.
Is there any easy way to use a shared memory segment which is larger
than 2GB?
Kind regards,
Robert
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL on FreeBSD 7.0 amd64 with more than 2GB shared memory
fails again with ENOMEM. Is there any easy way to use a shared memory segment which is larger than 2GB? getting two smaller ? :) no idea - maybe it's bug of SHM. as you already checked it please do sent-pr ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: PostgreSQL on FreeBSD 7.0 amd64 with more than 2GB shared memory
I just found a bug report for that issue: http://www.freebsd.org/cgi/query-pr.cgi?pr=121423cat= Thanks, Robert -Original Message- From: Wojciech Puchar [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 10. Dezember 2008 18:30 To: Hell, Robert Cc: freebsd-questions@freebsd.org Subject: Re: PostgreSQL on FreeBSD 7.0 amd64 with more than 2GB shared memory fails again with ENOMEM. Is there any easy way to use a shared memory segment which is larger than 2GB? getting two smaller ? :) no idea - maybe it's bug of SHM. as you already checked it please do sent-pr ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
PostgreSQL 8.0.3 + FreeBSD + TCP/IP
Hi, I'm having a difficulty getting PostgreSQL to accept TCP/IP connections on FreeBSD 5.3. I have edited 'postgresql.conf' in my postgres data directory to set the listen_address (and uncommented it) and have the port line uncommented and set to the default 5432. I then restarted the postmaster and tried to connect. I get: could not connect to server: Connection refused Is the server running on host xx.xxx.xx.xxx and accepting TCP/IP connections on port 5432? I can connect from localhost just fine. Is there anything that needs to be set in /etc/inetd.conf or /etc/hosts.allow? I have postgresql_enable=YES in my /etc/rc.conf file, but have not rebooted since I added that. If that's the problem, is there a good way to load that value without rebooting? Is it just an environmental variable? Thanks, Joe Koenig Production Manager jWeb New Media Design [EMAIL PROTECTED] http://www.jwebmedia.com/ 636.928.3162 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL 8.0.3 + FreeBSD + TCP/IP
On Tue, 2005-06-14 at 10:05 -0500, Joseph Koenig (jWeb) wrote: Hi, I'm having a difficulty getting PostgreSQL to accept TCP/IP connections on FreeBSD 5.3. I have edited 'postgresql.conf' in my postgres data directory to set the listen_address (and uncommented it) and have the port line uncommented and set to the default 5432. I then restarted the postmaster and tried to connect. I get: could not connect to server: Connection refused Is the server running on host xx.xxx.xx.xxx and accepting TCP/IP connections on port 5432? I can connect from localhost just fine. Is there anything that needs to be set in /etc/inetd.conf or /etc/hosts.allow? I have postgresql_enable=YES in my /etc/rc.conf file, but have not rebooted since I added that. If that's the problem, is there a good way to load that value without rebooting? Is it just an environmental variable? Thanks, Joe Koenig Production Manager jWeb New Media Design [EMAIL PROTECTED] http://www.jwebmedia.com/ 636.928.3162 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- see pg_hba.conf in $PGDATA directory. :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL 8.0.3 + FreeBSD + TCP/IP
Hi, I'm having a difficulty getting PostgreSQL to accept TCP/IP connections on FreeBSD 5.3. I have edited 'postgresql.conf' in my postgres data directory to set the listen_address (and uncommented it) and have the port line uncommented and set to the default 5432. I then restarted the postmaster and tried to connect. I get: could not connect to server: Connection refused Is the server running on host xx.xxx.xx.xxx and accepting TCP/IP connections on port 5432? I can connect from localhost just fine. Is there anything that needs to be set in /etc/inetd.conf or /etc/hosts.allow? I have postgresql_enable=YES in my /etc/rc.conf file, but have not rebooted since I added that. If that's the problem, is there a good way to load that value without rebooting? Is it just an environmental variable? Thanks, Joe Koenig Production Manager jWeb New Media Design [EMAIL PROTECTED] http://www.jwebmedia.com/ 636.928.3162 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- see pg_hba.conf in $PGDATA directory. :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I guess I should have specified that I have already added the appropriate entries into pg_hba.conf. I thought that the error message would be enough to indicate it was not an authentication problem, as that generates an error stating there is not an entry in pg_hba for that host. Thanks, Joe Koenig Production Manager jWeb New Media Design [EMAIL PROTECTED] http://www.jwebmedia.com/ 636.928.3162 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL 8.0.3 + FreeBSD + TCP/IP
On Tue, 2005-06-14 at 10:05 -0500, Joseph Koenig (jWeb) wrote: Hi, I'm having a difficulty getting PostgreSQL to accept TCP/IP connections on FreeBSD 5.3. I have edited 'postgresql.conf' in my postgres data directory to set the listen_address (and uncommented it) and have the port line uncommented and set to the default 5432. I then restarted the postmaster and tried to connect. I get: could not connect to server: Connection refused Is the server running on host xx.xxx.xx.xxx and accepting TCP/IP connections on port 5432? I can connect from localhost just fine. Is there anything that needs to be set in /etc/inetd.conf or /etc/hosts.allow? I have postgresql_enable=YES in my /etc/rc.conf file, but have not rebooted since I added that. If that's the problem, is there a good way to load that value without rebooting? Is it just an environmental variable? Thanks, Joe Koenig Production Manager jWeb New Media Design [EMAIL PROTECTED] http://www.jwebmedia.com/ 636.928.3162 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] also check how database is started. example: pg_ctl start -D $PGDATA -o -i Options -i listen tcp connection. -- Kalashnikov Ilya [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL 8.0.3 + FreeBSD + TCP/IP
On Tue, Jun 14, 2005 at 10:05:05AM -0500, Joseph Koenig (jWeb) wrote: Hi, I'm having a difficulty getting PostgreSQL to accept TCP/IP connections on FreeBSD 5.3. I have edited 'postgresql.conf' in my postgres data directory to set the listen_address (and uncommented it) and have the port line uncommented and set to the default 5432. I then restarted the postmaster and tried to connect. I get: could not connect to server: Connection refused Is the server running on host xx.xxx.xx.xxx and accepting TCP/IP connections on port 5432? I can connect from localhost just fine. You need to set listen_addresses, like it says in the comments: listen_addresses = '*' This will allow Postgresql connections from all interfaces. -- Jonathan Chen [EMAIL PROTECTED] -- When all else fails, RTFM ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL 8.0.3 + FreeBSD + TCP/IP
On Tue, Jun 14, 2005 at 10:05:05AM -0500, Joseph Koenig (jWeb) wrote: Hi, I'm having a difficulty getting PostgreSQL to accept TCP/IP connections on FreeBSD 5.3. I have edited 'postgresql.conf' in my postgres data directory to set the listen_address (and uncommented it) and have the port line uncommented and set to the default 5432. I then restarted the postmaster and tried to connect. I get: could not connect to server: Connection refused Is the server running on host xx.xxx.xx.xxx and accepting TCP/IP connections on port 5432? I can connect from localhost just fine. You need to set listen_addresses, like it says in the comments: listen_addresses = '*' This will allow Postgresql connections from all interfaces. I have already tried setting the listen_addresses to * and the actual IP. Neither of which has worked. I restarted the postmaster both times using the script in /usr/local/etc/rc.d/, and by using pg_ctl. Even tried starting postmaster with pg_ctl -i. Nothing seems to be working. I have double-checked all of my pg_hba.conf settings, even though the error doesn't indicate that is the problem at all. Anyone else have any ideas at all? Thanks, Joe Koenig Production Manager jWeb New Media Design [EMAIL PROTECTED] http://www.jwebmedia.com/ 636.928.3162 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL 8.0.3 + FreeBSD + TCP/IP
On Tuesday 14 June 2005 03:14 pm, Joseph Koenig (jWeb) wrote: On Tue, Jun 14, 2005 at 10:05:05AM -0500, Joseph Koenig (jWeb) wrote: Hi, I'm having a difficulty getting PostgreSQL to accept TCP/IP connections on FreeBSD 5.3. I have edited 'postgresql.conf' in my postgres data directory to set the listen_address (and uncommented it) and have the port line uncommented and set to the default 5432. I then restarted the postmaster and tried to connect. I get: could not connect to server: Connection refused Is the server running on host xx.xxx.xx.xxx and accepting TCP/IP connections on port 5432? I can connect from localhost just fine. You need to set listen_addresses, like it says in the comments: listen_addresses = '*' This will allow Postgresql connections from all interfaces. I have already tried setting the listen_addresses to * and the actual IP. Neither of which has worked. I restarted the postmaster both times using the script in /usr/local/etc/rc.d/, and by using pg_ctl. Even tried starting postmaster with pg_ctl -i. Nothing seems to be working. I have double-checked all of my pg_hba.conf settings, even though the error doesn't indicate that is the problem at all. Anyone else have any ideas at all? Thanks, Joe Koenig Production Manager jWeb New Media Design [EMAIL PROTECTED] http://www.jwebmedia.com/ 636.928.3162 Have you checked the firewall settings on both computers to ensure that port 5432 is open? Andrew Gould ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL 8.0.3 + FreeBSD + TCP/IP
On Tuesday 14 June 2005 03:14 pm, Joseph Koenig (jWeb) wrote: On Tue, Jun 14, 2005 at 10:05:05AM -0500, Joseph Koenig (jWeb) wrote: Hi, I'm having a difficulty getting PostgreSQL to accept TCP/IP connections on FreeBSD 5.3. I have edited 'postgresql.conf' in my postgres data directory to set the listen_address (and uncommented it) and have the port line uncommented and set to the default 5432. I then restarted the postmaster and tried to connect. I get: could not connect to server: Connection refused Is the server running on host xx.xxx.xx.xxx and accepting TCP/IP connections on port 5432? I can connect from localhost just fine. You need to set listen_addresses, like it says in the comments: listen_addresses = '*' This will allow Postgresql connections from all interfaces. I have already tried setting the listen_addresses to * and the actual IP. Neither of which has worked. I restarted the postmaster both times using the script in /usr/local/etc/rc.d/, and by using pg_ctl. Even tried starting postmaster with pg_ctl -i. Nothing seems to be working. I have double-checked all of my pg_hba.conf settings, even though the error doesn't indicate that is the problem at all. Anyone else have any ideas at all? Thanks, Joe Koenig Production Manager jWeb New Media Design [EMAIL PROTECTED] http://www.jwebmedia.com/ 636.928.3162 Have you checked the firewall settings on both computers to ensure that port 5432 is open? Andrew Gould I'm guessing that opening the port is part of what placing postgresql_enable=YES in the rc.conf file does, correct? If so, that's probably the problem as I have not rebooted since adding that. Is there a way to safely force that to run without rebooting? There is a hardware firewall in front of the server that I have ensured is allowing that port through. Thanks, Joe Koenig Production Manager jWeb New Media Design [EMAIL PROTECTED] http://www.jwebmedia.com/ 636.928.3162 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL 8.0.3 + FreeBSD + TCP/IP
On Jun 14, 2005, at 4:46 PM, Joseph Koenig (jWeb) wrote: I'm guessing that opening the port is part of what placing postgresql_enable=YES in the rc.conf file does, correct? If so, that's probably the problem as I have not rebooted since adding that. Is there a way to safely force that to run without rebooting? There is a hardware firewall in front of the server that I have ensured is allowing that port through. Thanks, Joe Koenig Production Manager jWeb New Media Design [EMAIL PROTECTED] http://www.jwebmedia.com/ 636.928.3162 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] !DSPAM:42af4251253444259514897! Hi Joe, You can confirm whether or not port 5432 is opened by typing netstat -na | grep 5432 on your database server. You should not have to reboot for the port to be opened. When PostgreSQL starts, (either by starting it manually, or then the machine boots) it will open the port. IIt definitely sounds like the firewall could be your problem. I'd try connecting to the database server's port 5432 via telnet from an outside location, so that your packets have to pass thru the firewall in question. Thanks, Ken Ebling Ideal Internet, Inc. 561-963-4501 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL 8.0.3 + FreeBSD + TCP/IP
On Tuesday 14 June 2005 15:14, Joseph Koenig (jWeb) wrote: On Tue, Jun 14, 2005 at 10:05:05AM -0500, Joseph Koenig (jWeb) wrote: Hi, I'm having a difficulty getting PostgreSQL to accept TCP/IP connections on FreeBSD 5.3. I have edited 'postgresql.conf' in my postgres data directory to set the listen_address (and uncommented it) and have the port line uncommented and set to the default 5432. I then restarted the postmaster and tried to connect. I get: could not connect to server: Connection refused Is the server running on host xx.xxx.xx.xxx and accepting TCP/IP connections on port 5432? I can connect from localhost just fine. You need to set listen_addresses, like it says in the comments: listen_addresses = '*' This will allow Postgresql connections from all interfaces. I have already tried setting the listen_addresses to * and the actual IP. Neither of which has worked. I restarted the postmaster both times using the script in /usr/local/etc/rc.d/, and by using pg_ctl. Even tried starting postmaster with pg_ctl -i. Nothing seems to be working. I have double-checked all of my pg_hba.conf settings, even though the error doesn't indicate that is the problem at all. Anyone else have any ideas at all? Thanks, Joe Koenig Production Manager jWeb New Media Design [EMAIL PROTECTED] http://www.jwebmedia.com/ 636.928.3162 What do you get when you telnet localhost 5432 verses telnet otherserver 5432 ? Try this to rule out any sort of firewall/tunnelling issues If it hangs and you get no prompt, but drops after you type 2 or 3 letters then it means postmaster is doing the negotiation (so then you check the postmaster log). Otherwise you've got gnats in your firewall (or some other kind of bug) to deal with. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL 8.0.3 + FreeBSD + TCP/IP (Solved)
On Jun 14, 2005, at 4:46 PM, Joseph Koenig (jWeb) wrote: I'm guessing that opening the port is part of what placing postgresql_enable=YES in the rc.conf file does, correct? If so, that's probably the problem as I have not rebooted since adding that. Is there a way to safely force that to run without rebooting? There is a hardware firewall in front of the server that I have ensured is allowing that port through. Thanks, Joe Koenig Production Manager jWeb New Media Design [EMAIL PROTECTED] http://www.jwebmedia.com/ 636.928.3162 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] !DSPAM:42af4251253444259514897! Hi Joe, You can confirm whether or not port 5432 is opened by typing netstat -na | grep 5432 on your database server. You should not have to reboot for the port to be opened. When PostgreSQL starts, (either by starting it manually, or then the machine boots) it will open the port. IIt definitely sounds like the firewall could be your problem. I'd try connecting to the database server's port 5432 via telnet from an outside location, so that your packets have to pass thru the firewall in question. Thanks, Ken Ebling Ideal Internet, Inc. 561-963-4501 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Thanks to Ken and everyone who sent in recommendations - looks like it was an issue of a network admin who assured me the firewall was open when it really wasn't... Joe Koenig Production Manager jWeb New Media Design [EMAIL PROTECTED] http://www.jwebmedia.com/ 636.928.3162 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL on FreeBSD
On Mon, Oct 27, 2003 at 04:04:28PM -0500, Lowell Gilbert wrote: Why does setting them in /etc/sysctl.conf or /etc/loader.conf not work ? You're doing something wrong. That's all I can say when the description of the failure is just not work. Allow me to expand on that then... I put the options in /etc/sysctl.conf as follows: kern.ipc.somaxconn=512 kern.ipc.shmmax=268435456 kern.ipc.shmall=65536 kern.ipc.shmmni=128 kern.ipc.semmns=256 When I reboot, sysctl -a | grep kern.ipc.semmns returns kern.ipc.semmns: 60 -- Wayne Pascoe The time for action is passed. Now is the time for senseless bickering. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL on FreeBSD
On Tue, 28 Oct 2003, Wayne Pascoe wrote: On Mon, Oct 27, 2003 at 04:04:28PM -0500, Lowell Gilbert wrote: Why does setting them in /etc/sysctl.conf or /etc/loader.conf not work ? You're doing something wrong. That's all I can say when the description of the failure is just not work. Allow me to expand on that then... I put the options in /etc/sysctl.conf as follows: kern.ipc.somaxconn=512 kern.ipc.shmmax=268435456 kern.ipc.shmall=65536 kern.ipc.shmmni=128 kern.ipc.semmns=256 When I reboot, sysctl -a | grep kern.ipc.semmns returns kern.ipc.semmns: 60 I believe -current now has code to pull values for these out of the kernel environment; that's missing in -stable (IIRC; not checked, but I have a vague recollection of trying to figure out how the hell the values were supposed to get into the sysctl value until I looked at the -current tree). -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287088 Fax +44 (0)117 9287112 http://ioctl.org/jan/ I like oranges more than apples!? - that's like comparing apples and oranges! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL on FreeBSD
Wayne Pascoe [EMAIL PROTECTED] writes: On Mon, Oct 27, 2003 at 04:04:28PM -0500, Lowell Gilbert wrote: Why does setting them in /etc/sysctl.conf or /etc/loader.conf not work ? You're doing something wrong. That's all I can say when the description of the failure is just not work. Allow me to expand on that then... I put the options in /etc/sysctl.conf as follows: kern.ipc.somaxconn=512 kern.ipc.shmmax=268435456 kern.ipc.shmall=65536 kern.ipc.shmmni=128 kern.ipc.semmns=256 When I reboot, sysctl -a | grep kern.ipc.semmns returns kern.ipc.semmns: 60 Hmm. I just checked, and it's working fine for me under yesterday's -STABLE. Are you getting any error messages at boot when sysctl.conf is evaluated? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
PostgreSQL on FreeBSD
Hi all, I'm trying to configure and tune postgresql on FreeBSD 4.9. We want to allow at least 128 concurrent connections but preferably 256. Looking at the documentation, we should be okay if we set the following in our kernel to achieve this: kern.ipc.somaxconn = 512 kern.ipc.shmall = 65536 kern.ipc.shmmni = 128 kern.ipc.semmni = 8 kern.ipc.semmns = 256 Now, I have three questions... 1. Why do we have to set these in the kernel ? Why does setting them in /etc/sysctl.conf or /etc/loader.conf not work ? 2. Is there a recommended list of settings that we should use in our kernel to allow 128 connections and 256 connections ? and lastly, 3. What is the impact on the rest of the system likely to be by setting aside this memory as shared memory ? Is it then no longer available to other applications like Apache and Exim ? Are there any other performance issues that we should be aware of ? Regards, -- Wayne Pascoe Be nice to your daemons. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL on FreeBSD
I'm trying to configure and tune postgresql on FreeBSD 4.9. We want to allow at least 128 concurrent connections but preferably 256. My memory is that there was some extensive discussion of this on the freebsd-databases mailing list, and a search of the archives at lists.freebsd.org should turn them up. Mike Squires ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL on FreeBSD
I haven't used that software since it was called postgres, but I'll wade in anyway... Wayne Pascoe [EMAIL PROTECTED] writes: Hi all, I'm trying to configure and tune postgresql on FreeBSD 4.9. We want to allow at least 128 concurrent connections but preferably 256. Looking at the documentation, we should be okay if we set the following in our kernel to achieve this: kern.ipc.somaxconn = 512 kern.ipc.shmall = 65536 kern.ipc.shmmni = 128 kern.ipc.semmni = 8 kern.ipc.semmns = 256 Now, I have three questions... 1. Why do we have to set these in the kernel ? You don't. Why does setting them in /etc/sysctl.conf or /etc/loader.conf not work ? You're doing something wrong. That's all I can say when the description of the failure is just not work. 2. Is there a recommended list of settings that we should use in our kernel to allow 128 connections and 256 connections ? A single recommendation, no. It's been discussed. You started with tuning(7), I assume. and lastly, 3. What is the impact on the rest of the system likely to be by setting aside this memory as shared memory ? Is it then no longer available to other applications like Apache and Exim ? Are there any other performance issues that we should be aware of ? Yes, the memory is pulled out of the general pool, and no, I don't think there will be any other noticeable effects at those settings. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
MySQL or Postgresql on FreeBSD, have I just started a holy war?
Hi all, I've just been getting ready to start serious MySQL development on a Dual Processor FreeBSD box and I stumbled across the following blog entry on the web today which has me thinking: http://jeremy.zawodny.com/blog/archives/000203.html#000203 The coles notes version is that the author, who seems to have some chops in both MySQL and FreeBSD (looks like he's a sysadmin at Yahoo, hi if you're out there Jeremy), has come across some issues with threading and smp support while using MySQL FreeBSD. Now, of course, he doesn't mention is the machines where these issues come up are super high traffic or not, so this may be all moot if you're not running say, Yahoo! I'm still a babe in the woods when it comes to MySQL, but I'm redeveloping several databases that I did some time ago in a proprietary database solution (4D) and I'll be damned if I'm going to redo these things again any time soon, so I'd like to know that I've made the right choice of DB Platform. I've been really happy with 4D overall, but need to have more connectivity options, hence the move. There must be a ton of people running MySQL on FreeBSD, so my first question is, are the issues raised here ones likely to occur on a low to medium volume system? I'm doing about 100,000 queries a day on our current db server from a variety of websites and would expect this volume to double or triple in the next year. My FreeBSD Box is currently DP PIII 500's, but I'll be upgrading it to Ghz PIII's before deployment with a gig of RAM, more if needed. My current DB server is actually an iMac, it's a long story, with a 400Mhz G3 and 512 mb RAM running OS X 10.2 and keeping up quite nicely, so I don't imagine the hardware itself will be a limiting factor. My second question is, if it looks like this will potentially be an issue, how does Postgresql perform on FreeBSD. I could use it just as easily as MySQL and, from what I've heard, it's a little beefier in some aspects. With regards to threading issues, am I likely to be happier with Postgresql in the long term? Our current DB server runs for _MONTHS_ at a time without me even having to look at it, so reliability is the key factor in my decision process. Moving away from FreeBSD is not an option I'd like to consider at the moment, as I'm quite happy with it so far, so I'd like to pick the db that likes FreeBSD the best. Sorry if I just started a holy war, I promise not to ask about Postfix v Qmail! :-) Tom Wiebe To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: MySQL or Postgresql on FreeBSD, have I just started a holy war?
Mailing Lists wrote: Hi all, I've just been getting ready to start serious MySQL development on a Dual Processor FreeBSD box and I stumbled across the following blog entry on the web today which has me thinking: http://jeremy.zawodny.com/blog/archives/000203.html#000203 The coles notes version is that the author, who seems to have some chops in both MySQL and FreeBSD (looks like he's a sysadmin at Yahoo, hi if you're out there Jeremy), has come across some issues with threading and smp support while using MySQL FreeBSD. Now, of course, he doesn't mention is the machines where these issues come up are super high traffic or not, so this may be all moot if you're not running say, Yahoo! I'm still a babe in the woods when it comes to MySQL, but I'm redeveloping several databases that I did some time ago in a proprietary database solution (4D) and I'll be damned if I'm going to redo these things again any time soon, so I'd like to know that I've made the right choice of DB Platform. I've been really happy with 4D overall, but need to have more connectivity options, hence the move. There must be a ton of people running MySQL on FreeBSD, so my first question is, are the issues raised here ones likely to occur on a low to medium volume system? I'm doing about 100,000 queries a day on our current db server from a variety of websites and would expect this volume to double or triple in the next year. My FreeBSD Box is currently DP PIII 500's, but I'll be upgrading it to Ghz PIII's before deployment with a gig of RAM, more if needed. My current DB server is actually an iMac, it's a long story, with a 400Mhz G3 and 512 mb RAM running OS X 10.2 and keeping up quite nicely, so I don't imagine the hardware itself will be a limiting factor. My second question is, if it looks like this will potentially be an issue, how does Postgresql perform on FreeBSD. I could use it just as easily as MySQL and, from what I've heard, it's a little beefier in some aspects. With regards to threading issues, am I likely to be happier with Postgresql in the long term? Im far from skilled in SQL and databases, but I have used postgre on FreeBSD for some time, and never had any problems. I run a few db's, the biggest probably around 25000 rows and maybe 300 hits a day, so I cant really say its under any kind of load worth mentioning. However, I have tried to stress it a bit with a few simple perl scripts bombing it with queries. On a dual PII 233 with 256M ram I couldnt even make it break a sweat. As I said, Im no SQL guru, my very primitive benchmark was just a few perl loops sending queries as fast as they could. No matter how I tried I couldnt even notice any impact on the machine's performance...I guess the SQL answered faster then my perl loops could generate queries. :) From what I've read and experienced, postgre seems to be an excellent choice on FreeBSD. And I do love FreeBSD, but to me this sound like the old use whatever gets the job done saying. If linux can do what you want and do it good, you really shouldnt run it on BSD just for the sake of it. -- R To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: MySQL or Postgresql on FreeBSD, have I just started a holy war?
IIRC, the site owner at phpbuilder.com has done some research on this and has a solid opinion. It may match Jeremy's, but I can't remember at the moment. You might grok his search routine and get another opinion. Kevin Kinsey, DaleCo, S.P. - Original Message - From: Roger 'Rocky' Vetterberg [EMAIL PROTECTED] To: Mailing Lists [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, October 02, 2002 5:52 AM Subject: Re: MySQL or Postgresql on FreeBSD, have I just started a holy war? Mailing Lists wrote: Hi all, I've just been getting ready to start serious MySQL development on a Dual Processor FreeBSD box and I stumbled across the following blog entry on the web today which has me thinking: http://jeremy.zawodny.com/blog/archives/000203.html#000203 The coles notes version is that the author, who seems to have some chops in both MySQL and FreeBSD (looks like he's a sysadmin at Yahoo, hi if you're out there Jeremy), has come across some issues with threading and smp support while using MySQL FreeBSD. Now, of course, he doesn't mention is the machines where these issues come up are super high traffic or not, so this may be all moot if you're not running say, Yahoo! I'm still a babe in the woods when it comes to MySQL, but I'm redeveloping several databases that I did some time ago in a proprietary database solution (4D) and I'll be damned if I'm going to redo these things again any time soon, so I'd like to know that I've made the right choice of DB Platform. I've been really happy with 4D overall, but need to have more connectivity options, hence the move. There must be a ton of people running MySQL on FreeBSD, so my first question is, are the issues raised here ones likely to occur on a low to medium volume system? I'm doing about 100,000 queries a day on our current db server from a variety of websites and would expect this volume to double or triple in the next year. My FreeBSD Box is currently DP PIII 500's, but I'll be upgrading it to Ghz PIII's before deployment with a gig of RAM, more if needed. My current DB server is actually an iMac, it's a long story, with a 400Mhz G3 and 512 mb RAM running OS X 10.2 and keeping up quite nicely, so I don't imagine the hardware itself will be a limiting factor. My second question is, if it looks like this will potentially be an issue, how does Postgresql perform on FreeBSD. I could use it just as easily as MySQL and, from what I've heard, it's a little beefier in some aspects. With regards to threading issues, am I likely to be happier with Postgresql in the long term? Im far from skilled in SQL and databases, but I have used postgre on FreeBSD for some time, and never had any problems. I run a few db's, the biggest probably around 25000 rows and maybe 300 hits a day, so I cant really say its under any kind of load worth mentioning. However, I have tried to stress it a bit with a few simple perl scripts bombing it with queries. On a dual PII 233 with 256M ram I couldnt even make it break a sweat. As I said, Im no SQL guru, my very primitive benchmark was just a few perl loops sending queries as fast as they could. No matter how I tried I couldnt even notice any impact on the machine's performance...I guess the SQL answered faster then my perl loops could generate queries. :) From what I've read and experienced, postgre seems to be an excellent choice on FreeBSD. And I do love FreeBSD, but to me this sound like the old use whatever gets the job done saying. If linux can do what you want and do it good, you really shouldnt run it on BSD just for the sake of it. -- R To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: MySQL or Postgresql on FreeBSD, have I just started a holy war?
Hello, I'm a PostgreSQL person so take all my comments with that in mind. On Wed, 2 Oct 2002 03:06:37 -0700 Mailing Lists [EMAIL PROTECTED] wrote: Hi all, I've just been getting ready to start serious MySQL development on a Dual Processor FreeBSD box and I stumbled across the following blog entry on the web today which has me thinking: http://jeremy.zawodny.com/blog/archives/000203.html#000203 The coles notes version is that the author, who seems to have some chops in both MySQL and FreeBSD (looks like he's a sysadmin at Yahoo, hi if you're out there Jeremy), has come across some issues with threading and smp support while using MySQL FreeBSD. Now, of course, he doesn't mention is the machines where these issues come up are super high traffic or not, so this may be all moot if you're not running say, Yahoo! For the kind of traffic your talking about, either system (MySQL or PostgreSQL) would work just fine. I'm still a babe in the woods when it comes to MySQL, but I'm redeveloping several databases that I did some time ago in a proprietary database solution (4D) and I'll be damned if I'm going to redo these things again any time soon, so I'd like to know that I've made the right choice of DB Platform. I've been really happy with 4D overall, but need to have more connectivity options, hence the move. Everything being about equal at this point for you, look at the available features. Do you use subselects, procedures, triggers, FK or transactions? Yes, I know that the latest development versions of MySQL support FK and transactions, but in this case you loose hot backups (ie when the server is up) unless your willing to pay for the util. There must be a ton of people running MySQL on FreeBSD, so my first question is, are the issues raised here ones likely to occur on a low to medium volume system? I'm doing about 100,000 queries a day on our current db server from a variety of websites and would expect this volume to double or triple in the next year. 100,000 to 400,000 trans a day should be nothing to any decent database. This is only about 1 to 4 transactions a second. I've handled this kind of load using DBM files with perl. My FreeBSD Box is currently DP PIII 500's, but I'll be upgrading it to Ghz PIII's before deployment with a gig of RAM, more if needed. My current DB server is actually an iMac, it's a long story, with a 400Mhz G3 and 512 mb RAM running OS X 10.2 and keeping up quite nicely, so I don't imagine the hardware itself will be a limiting factor. My second question is, if it looks like this will potentially be an issue, how does Postgresql perform on FreeBSD. I could use it just as easily as MySQL and, from what I've heard, it's a little beefier in some aspects. With regards to threading issues, am I likely to be happier with Postgresql in the long term? PostgreSQL is non-threaded so that is a moot point. PostgreSQL works quite well on FreeBSD under heavy load. I've got a system (1,000,000+ rows) that takes 3 to 10 connections a second without a sweat running on a PIII 800 1000MB SCSI system. Mind you, this is mostly insert transactions. Our current DB server runs for _MONTHS_ at a time without me even having to look at it, so reliability is the key factor in my decision process. Moving away from FreeBSD is not an option I'd like to consider at the moment, as I'm quite happy with it so far, so I'd like to pick the db that likes FreeBSD the best. I've got automatic monitoring on my high load system to watch my diskspace and with some of my scripts to delete old data (it monitors a set of web sites in real time), I forget it's there until the next time someone requests a new feature. Sorry if I just started a holy war, I promise not to ask about Postfix v Qmail! :-) Tom Wiebe To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message Hopefully it helps. GB -- GB Clark II | Roaming FreeBSD Admin [EMAIL PROTECTED] | General Geek CTHULU for President - Why choose the lesser of two evils? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: MySQL or Postgresql on FreeBSD, have I just started a holy war?
I am a Postgresql person myself. I can say there is one bad thing about Postgres that might be annoying to some. When data is deleted, the disk space is not recovered until a manual vacuum takes place. On a high load system with many updates or deletes, this could be a real headache. A cron job would probably fill role nicely. Tom Veldhouse - Original Message - From: GB Clark [EMAIL PROTECTED] To: Mailing Lists [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, October 02, 2002 7:05 AM Subject: Re: MySQL or Postgresql on FreeBSD, have I just started a holy war? Hello, I'm a PostgreSQL person so take all my comments with that in mind. On Wed, 2 Oct 2002 03:06:37 -0700 Mailing Lists [EMAIL PROTECTED] wrote: To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
