Altho its very tempting to get into an OS-war here, its not worth the time
it would take...its the reason why I sent my comments to Murali privately,
too bad he deemed that it was something to comment on publicly ;(
On Thu, 16 Dec 1999, Differentiated Software Solutions
Pvt. Ltd. wrote:
> Hi,
>
> Thanks for your reply....
>
> I have 2 problems
> a) Too many files open which is coming from Linux,where your point is well
> taken about not using Linux
> b) Spinlock error. In my opinion I don't think Linux has anything to do with
> it directly at least.
>
> I did look at the bug fixes of the newer version couldn't find any directly
> connected with this problem.
> I know I can fix too many open files problem... but am not sure how to fix
> spin lock problem.
>
> Aside from all this.... I presume you are in some way actively contributing
> to postgres development. It being a free db and shareware and all that.....
> I think majority of postgres users will be on Linux and some of them using
> it for Server application.
> I'm very tempted to start a vote campaign to prove to you how many people
> are using Postgres on Linux as a server application.
>
> Thanks again for your help. If you have any more thots on this problem I'll
> be very glad
>
> Murali
> -----Original Message-----
> From: The Hermit Hacker <scrappy@hub.org>
> To: Differentiated Software Solutions Pvt. Ltd. <diffs@vsnl.com>
> Date: 16 December 1999 00:03
> Subject: Re: [GENERAL] Re: Fw: Spin lock error
>
>
> >On Wed, 15 Dec 1999, Differentiated Software Solutions Pvt. Ltd. wrote:
> >
> >> Hi,
> >>
> >> Oops.... I'm sorry. Don't know why I missed it out
> >> It is postgres 6.5.1.
> >
> >Okay, I don't have any love for Linux, or trust in it, so I can't be of
> >much help (you couldn't pay me to use Linux for a server application
> >*shrug*)
> >
> >The other question is what is your hardware like? RAM? Drives? etc...
> >
> >So, you should send this out to the list to help on that front, and
> >looking at the release notes for 6.5.2, nothing *appears* to jump out,
> >which isn't to say that something fixed below doesn't indirectly affect
> >you. My only/first suggestion is to upgrade to v6.5.3 and see if that
> >helps any, then go from there...
> >
> >subselect+CASE fixes(Tom)
> >Add SHLIB_LINK setting for solaris_i386 and solaris_sparc ports(Daren
> Sefcik)
> >Fixes for CASE in WHERE join clauses(Tom)
> >Fix BTScan abort(Tom)
> >Repair the check for redundant UNIQUE and PRIMARY KEY indices(Thomas)
> >Improve it so that it checks for multi-column constraints(Thomas)
> >Fix for Win32 making problem with MB enabled(Hiroki Kataoka)
> >Allow BSD yacc and bison to compile pl code(Bruce)
> >Fix SET NAMES working
> >int8 fixes(Thomas)
> >Fix vacuum's memory consumption(Hiroshi,Tatsuo)
> >Reduce the total memory consumption of vacuum(Tom)
> >Fix for timestamp(datetime)
> >Rule deparsing bugfixes(Tom)
> >Fix quoting problems in mkMakefile.tcldefs.sh.in and
> mkMakefile.tkdefs.sh.in(Tom)
> >This is to re-use space on index pages freed by vacuum(Vadim)
> >document -x for pg_dump(Bruce)
> >Fix for unary operators in rule deparser(Tom)
> >Comment out FileUnlink of excess segments during mdtruncate()(Tom)
> >Irix linking fix from Yu Cao yucao@falcon.kla-tencor.com
> >Repair logic error in LIKE: should not return LIKE_ABORT
> > when reach end of pattern before end of text(Tom)
> >Repair incorrect cleanup of heap memory allocation during transaction
> abort(Tom)
> >Updated version of pgaccess 0.98
> >
> >
> >>
> >> Murali
> >> -----Original Message-----
> >> From: The Hermit Hacker <scrappy@hub.org>
> >> To: Differentiated Software Solutions Pvt. Ltd. <diffs@vsnl.com>
> >> Cc: pgsql-general@postgreSQL.org <pgsql-general@postgreSQL.org>
> >> Date: 15 December 1999 11:11
> >> Subject: [GENERAL] Re: Fw: Spin lock error
> >>
> >>
> >> >
> >> >I seem to still be missing what version of PostgreSQL you are
> >>
> ..:(
> >> >
> >> >On Wed, 15 Dec 1999, Differentiated Software Solutions Pvt. Ltd. wrote:
> >> >
> >> >> Hi,
> >> >>
> >> >> Thanks for responding.
> >> >> This is a copy of my message which has all details which I could think of to
> >> >> start with.
> >> >> I would be glad to receive any suggesstions.
> >> >>
> >> >> Bye,
> >> >>
> >> >> Murali
> >> >> -----Original Message-----
> >> >> From: Differentiated Software Solutions Pvt. Ltd. +ADw-diffs+AEA-vsnl.com+AD4-
> >> >> To: pgsql-general+AEA-postgresql.org +ADw-pgsql-general+AEA-postgresql.org+AD4AOw-
>
> >> >> vadim+AEA-krs.ru +ADw-vadim+AEA-krs.ru+AD4AOw-
> pgsql-interfaces+AEA-postgresql.org
> >> >> +ADw-pgsql-interfaces+AEA-postgresql.org+AD4-
> >> >> Cc: Kimi +ADw-kimi+AEA-intercept.co.in+AD4-
> >> >> Date: 11 December 1999 12:33
> >> >> Subject: Spin lock error
> >> >>
> >> >>
> >> >> +AD4-Hi,
> >> >> +AD4-
> >> >> +AD4-We are getting spinlock errors under the following conditions
> >> >> +AD4-
> >> >> +AD4-Background :
> >> >> +AD4-We have developed a high performance application using postgres
> database
> >> >> a
> >> >> +AD4-3rd party application server).
> >> >> +AD4-This application should be scalanble to server 50 requests a
> second.
> >> >> +AD4-Application is written in perl 5.005 using DBI-1.12, DBD-Pg 0.92
> and Redhat
> >> >> +AD4-linux 6.0
> >> >> +AD4-A request consists of one singleton select on a table of 200,000
> rows on
> >> >> +AD4-it's primary key, a heavy duty cursor which is a 4 table join but
> which
> >> >> +AD4-returns 100 rows from tables containing maximum of 250 rows, a
> light sql
> >> >> +AD4-opening a cursor on a table containing 500 rows, 2 inserts into
> tables
> >> >> which
> >> >> +AD4-don't have primary key.
> >> >> +AD4-
> >> >> +AD4-We are connecting
> >> to the database with autoconnect off.
> >> >> +AD4-
> >> >> +AD4-Problem description :
> >> >> +AD4-On a light load there are no problems. As we have increased the
> load
> >> on the
> >> >> +AD4-application, the requests get piled up. We keep monitoring the
> >> requests
> >> >> +AD4-getting piled up using ps ax +AHw- grep post.
> >> >> +AD4-Somewhere when the requests crosses 20(ps returns more than 20
> >> rows)....
> >> >> +AD4-suddenly postmaster comes down +ACEAIQ- In the server log the
> >> following message
> >> >> is
> >> >> +AD4-written out.
> >> >> +AD4-FATAL: s+AF8-lock(4000b011) at spin.c:125, stuck spinlock.
> Aborting.
> >> >> +AD4-
> >> >> +AD4-FATAL: s+AF8-lock(4000b011) at spin.c:125, stuck spinlock.
> Aborting.
> >> >> +AD4-
> >> >> +AD4-FATAL: s+AF8-lock(4000b011) at spin.c:125, stuck spinlock.
> Aborting.
> >> >> +AD4-
> >> >> +AD4-FATAL: s+AF8-lock(4000b011) at spin.c:125, stuck spinlock.
> Aborting.
> >> >> +AD4-
> >> >> +AD4-FATAL: s+AF8-lock(40179f44) at bufmgr.c:490, stuck spinlock.
> >> Aborting.
> >> >> +AD4-After this postmaster shutdown.
> >> >> +AD4-
> >> >> +AD4-One observation If we try to recreate this in another linux
> >> machine...
> >> >> +AD4-multiple postmasters run in the linux machine when the number of
> >> requests
> >> >> +AD4-become more.
> >> >> +AD4-I'm also attaching a file containing 'ps' at the instance
> postmaster
> >> >> +AD4-crashed.
> >> >> +AD4-
> >> >> +AD4-Can anybody please help
> >> >> +AD4-
> >> >> +AD4-Thanks and regards,
> >> >> +AD4-
> >> >> +AD4-Murali
> >> >> +AD4-
> >> >> +AD4-Differentiated Software Solutions Pvt. Ltd.,
> >> >> +AD4-176, Gr. Floor, 6th Main
> >> >> +AD4-2nd Block RT Nagar
> >> >> +AD4-Bangalore - 560 032
> >> >> +AD4-India
> >> >> +AD4-Ph: 91 80 3431470
> >> >> +AD4-
> >> >>
> >> >
> >> >Marc G. Fournier ICQ#7615664 IRC Nick:
> >> Scrappy
> >> >Systems Administrator @ hub.org
> >> >primary: scrappy@hub.org secondary:
> >> scrappy@{freebsd|postgresql}.org
> >> >
> >> >
> >> >************
> >> >
> >> >
> >>
> >>
> >
> >Marc G. Fournier ICQ#7615664 IRC Nick:
> Scrappy
> >Systems Administrator @ hub.org
> >primary: scrappy@hub.org secondary:
> scrappy@{freebsd|postgresql}.org
> >
> >
>
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
