Re: [HACKERS] bad performance on irix
[EMAIL PROTECTED] (Luis Alberto Amigo Navarro) writes: we're running on sgi powerchallenge, 8 r1 4-way smp, and we're getting bad performance from postgres, throughput increases from 1 to 5 streams, but from 5 and above there is no further increase, performance analysis show high sleep waiting for resources IIRC there is a bottleneck on calls to sleep() or similar on IRIX SMP. All requests are dealt with on just one of the CPUs. I don't recollect whether there is a way to work around that or whether programs need to be rewritten. -- Pete Forman-./\.- Disclaimer: This post is originated WesternGeco -./\.- by myself and does not represent [EMAIL PROTECTED]-./\.- opinion of Schlumberger, Baker http://petef.port5.com (new)-./\.- Hughes or their divisions. ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
[HACKERS] initdb dies during IpcSemaphoreCreate under BSD jail
(posted last week to pgsql-general; no responses there, so I'm seeing if anyone here can contribute. Thanks!) I'm working on a site hosted in a BSD Jail; they have MySQL installed but, of course, I'd rather use PostgreSQL. It installs fine but can't initdb; get the following: Fixing permissions on existing directory /usr/local/pgsql/data... ok creating directory /usr/local/pgsql/data/base... ok creating directory /usr/local/pgsql/data/global... ok creating directory /usr/local/pgsql/data/pg_xlog... ok creating directory /usr/local/pgsql/data/pg_clog... ok creating template1 database in /usr/local/pgsql/data/base/1... IpcSemaphoreCreate: semget(key=1, num=17, 03600) failed: Function not implemented Earlier message traffic suggests that SYSV IPC has not been fixed to run under BSD Jails. The last time this was raised was ~1 year ago. Has there been any changes here that anyone knows of? Any hope of getting PG running in our jail? (Or, alternatively, can PG run on the real machine's processes so that the different jails can access it?) Any help would be appreciated! Thanks. Joel BURTON | [EMAIL PROTECTED] | joelburton.com | aim: wjoelburton Knowledge Management Technology Consultant ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] Antw: Re: patch for include/utils/datetime.h to target NetWare
Your assumption is correct. All I need is what you described: #ifdef __CYGWIN__ to #if defined(__CYGWIN__) || defined(N_PLAT_NLM) Great. I'll include that in a set of patches I'm working on. Sorry that the patchfile didn't include the context. I will make sure that this doesn't happen any more. No problem. Thanks for the patch! - Thomas ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] initdb dies during IpcSemaphoreCreate under BSD jail
On Mon, 25 Mar 2002, Joel Burton wrote: (posted last week to pgsql-general; no responses there, so I'm seeing if anyone here can contribute. Thanks!) I'm working on a site hosted in a BSD Jail; they have MySQL installed but, of course, I'd rather use PostgreSQL. It installs fine but can't initdb; get the following: Fixing permissions on existing directory /usr/local/pgsql/data... ok creating directory /usr/local/pgsql/data/base... ok creating directory /usr/local/pgsql/data/global... ok creating directory /usr/local/pgsql/data/pg_xlog... ok creating directory /usr/local/pgsql/data/pg_clog... ok creating template1 database in /usr/local/pgsql/data/base/1... IpcSemaphoreCreate: semget(key=1, num=17, 03600) failed: Function not implemented Earlier message traffic suggests that SYSV IPC has not been fixed to run under BSD Jails. The last time this was raised was ~1 year ago. Has there been any changes here that anyone knows of? Any hope of getting PG running in our jail? (Or, alternatively, can PG run on the real machine's processes so that the different jails can access it?) I don't know about running PG in a jail, but if you have it running on the parent or real machine the jails can access it just fine but not as localhost. Vince. -- == Vince Vielhaber -- KA8CSHemail: [EMAIL PROTECTED]http://www.pop4.net 56K Nationwide Dialup from $16.00/mo at Pop4 Networking Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] pg_control contents
Thomas Lockhart [EMAIL PROTECTED] writes: If LOCALE_NAME_BUFLEN changes size between writing and reading the control file, the CRC *could* still be calculated correctly. There might be some value to storing sizeof(ControlFileData) explicitly, so that that CRC calculation could be made. But I still see none in storing LOCALE_NAME_BUFLEN explicitly. There is *no* difference between I changed LOCALE_NAME_BUFLEN at random and I added or reordered fields in the struct at random. In either case the file has to be treated as completely useless, because we don't really know what's in there at what offset. And making either sort of change without bumping PG_CONTROL_VERSION is simply a mistake that we cannot afford to make. There are plenty of places in PG where ill-considered hacking will have undesirable consequences; pg_control is just one more. The value of storing sizeof(ControlFileData) explicitly would not be that we could hope to extract data safely, but only that we could distinguish corrupt data from good data in an incompatible format with marginally more reliability than now. But both of these are and must be failure cases, so it's really not that interesting to distinguish between them. regards, tom lane ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[HACKERS] Patch for xlog.c
Hello everybody,
If possible please add the following patch to better support NetWare.
best regards
Ulrich Neumann
Novell Worldwide Developer Support
begin 666 xlog.patch
M+2TM(%QP9W-Q;#R+F]R9UQSF-8F%C:V5N9%QA8V-EW-=')A;G-A;5QX
M;]G+F,)36]N($IA;B`Q-`Q-CHU-3HU.`R,#`R#0HK*RL@7'!GW%L-S(N
M95V7'-R8UQB86-K96YD7%C8V5SUQTF%NV%M7'AL;VN8PE-;VX@1F5B
M(#$Q(#`P.C0P.C$P(#(P,#(-D!`(TQ-#DS+#*S$T.3,L-R!`0`T*(`D
M*B!O=F5R=W)I=4@86X97AIW1I;F;]G9FEL92X($AO=V5V97(L('1H
M97)E('-H;W5L9XG=!B92!O;F4L('-O#0H2`J(')E;F%M92@I(ES(%N
M(%C8V5P=%B;4W5BW1I='5T92!E-E'0@9F]R('1H92!TG5L2!P
M87)A;F]I9X-B`)(HO#0HM(VEF;F1E9B!?7T)%3U-?7PT**R-I9B`A95F
M:6YE9A?7T)%3U-?7RD)B8(61E9FEN960H3E]03$%47TY,32D-B`):68
M*QI;FLH=UP%T:P%T:D/`P*0T*(`D)96QO9RA35$]0+`B;EN
M:R!FF]M(5S('1O(5S(AI;FET:6%L:7IA=EO;B!O9B!L;V9FEL92`E
M=2PV5G;65N=`E=2D@9F%I;5D.B`E;2(L#0H0D)('1M'!A=L('!A
0=L(QO9RPV5G*3L-``
`
end
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
[HACKERS] Patch for pqsignal.h
Hello everybody, i've found a little bug in pqsignal.h. Attached is the patch. (AuthBlockSig wasn't defined in one case). This problem is not specific to a special platform, it may target several platfroms. best regards Ulrich Neumann Novell Worldwide Developer Support begin 666 pqsignal.patch M+2TM(%QP9W-Q;#R+F]R9UQSF-:6YC;'5D95QL:6)P5QP7-I9VYA;YH M4UO;B!.;W8@,#4@,38Z-#8Z,S0@,C`P,0T**RLK(%QP9W-Q;#R+F1E=EQS MF-:6YC;'5D95QL:6)P5QP7-I9VYA;YH51U92!-87(@,C8@,#`Z,#`Z M,#`@,C`P,@T*0$`@+3(X+#@*S(X+#@@0$`-B`C95F:6YE(%!'7U-%5$U! M4TLH;6%S:RD)VEG')O8VUAVLH4TE'7U-%5$U!4TLL(UAVLL($Y53$PI M#0H@(V5LV4-B!E'1EFX@:6YT55N0FQO8VM3:6L#0HM0D)0FQO8VM3 M:6[#0HK0D)0FQO8VM3:6L#0HK0D)075T:$)L;V-K4VEG.PT*(`T*(-D M969I;F4@4$=?4T5434%32RAM87-K*0ES:6=S971M87-K*HH*EN=HI*UA 0VLI*2D-B`C96YD:68-@`` ` end ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] Patch for pqsignal.h
Please check current CVS or snapshot. I believe this is fixed. --- Ulrich Neumann wrote: Hello everybody, i've found a little bug in pqsignal.h. Attached is the patch. (AuthBlockSig wasn't defined in one case). This problem is not specific to a special platform, it may target several platfroms. best regards Ulrich Neumann Novell Worldwide Developer Support begin 666 pqsignal.patch M+2TM(%QP9W-Q;#R+F]R9UQSF-:6YC;'5D95QL:6)P5QP7-I9VYA;YH M4UO;B!.;W8@,#4@,38Z-#8Z,S0@,C`P,0T**RLK(%QP9W-Q;#R+F1E=EQS MF-:6YC;'5D95QL:6)P5QP7-I9VYA;YH51U92!-87(@,C8@,#`Z,#`Z M,#`@,C`P,@T*0$`@+3(X+#@*S(X+#@@0$`-B`C95F:6YE(%!'7U-%5$U! M4TLH;6%S:RD)VEG')O8VUAVLH4TE'7U-%5$U!4TLL(UAVLL($Y53$PI M#0H@(V5LV4-B!E'1EFX@:6YT55N0FQO8VM3:6L#0HM0D)0FQO8VM3 M:6[#0HK0D)0FQO8VM3:6L#0HK0D)075T:$)L;V-K4VEG.PT*(`T*(-D M969I;F4@4$=?4T5434%32RAM87-K*0ES:6=S971M87-K*HH*EN=HI*UA 0VLI*2D-B`C96YD:68-@`` ` end ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED]) -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup.| Drexel Hill, Pennsylvania 19026 ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
[HACKERS] Rolling v7.2.1 ...
Just before anyone asks where it is ... I'm just rolling v7.2.1 up right now and will let everyone know once its ready for a download ... I'll do up an announce in the morning unless anyone finds a flaw in it ... ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] Rolling v7.2.1 ...
Try her out and let me know if there are any problems ... the build looks clean, sizes all look right ... if no visible probs, will announce in the mroning ... On Mon, 25 Mar 2002, Marc G. Fournier wrote: Just before anyone asks where it is ... I'm just rolling v7.2.1 up right now and will let everyone know once its ready for a download ... I'll do up an announce in the morning unless anyone finds a flaw in it ... ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] Rolling v7.2.1 ...
Other than the documentation issues, I confirm the tarball looks good from here. regards, tom lane ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] SET NULL / SET NOT NULL
Christopher Kings-Lynne [EMAIL PROTECTED] writes: I have throught of at least two problems with changing nullability. The first is primary keys. I have to prevent people setting a column involved in a PK to null, right? Probably so. What about temporary tables - is there any reason they shouldn't be able to modify a temporary table? What about indices? Will twiddling the nullability break indices on a table in any way? And foreign keys - foreign keys only have to reference UNIQUE, right? The nullability isn't an issue? Lastly - in a multicolumn primary key, does EVERY column in the key need to be NOT NULL? Chris ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Rolling v7.2.1 ...
Marc G. Fournier writes: Try her out and let me know if there are any problems ... the build looks clean, sizes all look right ... ... but the contained documentation is for 7.3. -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[HACKERS] build of 7.2.1 on SCO Openserver and Unixware 7.1.1
Sorry for the package, but the following patch need to be applied to get the new verion compiled on SCO Openserver 5.0.5 and Unixware 7.1.1 pgsql-7.2.1.diff Description: Binary data ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
[HACKERS] PostgreSQL cross-reference using LXR
Has anyone ever considered setting up LXR to cross-reference pgsql source on developer.postgresql.org or maybe techdocs.postgresql.org? I have seen it used in a couple of projects (originally written for the Linux kernel; lxr.php.net is another user), and it seems pretty useful. I set one up if anyone wants to take a look: http://www.joeconway.com/lxr.pgsql/ It just needs apache, perl, glimpse, agrep, and a small amount of configuration (and of course a fresh copy of cvs tip). Joe ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] SET NULL / SET NOT NULL
Christopher Kings-Lynne [EMAIL PROTECTED] writes: What about temporary tables - is there any reason they shouldn't be able to modify a temporary table? I don't see one. What about indices? Will twiddling the nullability break indices on a table in any way? No, not as long as you aren't changing existing data in the table. And foreign keys - foreign keys only have to reference UNIQUE, right? The nullability isn't an issue? Not sure about that --- Stephan or Jan will know. Lastly - in a multicolumn primary key, does EVERY column in the key need to be NOT NULL? Yes, I believe so. regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] Rolling v7.2.1 ...
Peter Eisentraut [EMAIL PROTECTED] writes: Marc G. Fournier writes: Try her out and let me know if there are any problems ... the build looks clean, sizes all look right ... ... but the contained documentation is for 7.3. On the subject of contained documentation, I notice *** postgresql-7.2.1/doc/src/sgml/version.sgml Mon Mar 18 18:04:11 2002 --- REL7_2/doc/src/sgml/version.sgmlThu May 10 21:46:33 2001 *** *** 3,7 documentation. In text, use for example version; to refer to them. -- ! !entity version 7.2.1 ! !entity majorversion 7.2.1 --- 3,7 documentation. In text, use for example version; to refer to them. -- ! !entity version 7.2 ! !entity majorversion 7.2 Is this right, or should majorversion still be 7.2? Right offhand the latter seems correct ... regards, tom lane ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] Rolling v7.2.1 ...
Tom Lane wrote: Peter Eisentraut [EMAIL PROTECTED] writes: Marc G. Fournier writes: Try her out and let me know if there are any problems ... the build looks clean, sizes all look right ... ... but the contained documentation is for 7.3. On the subject of contained documentation, I notice *** postgresql-7.2.1/doc/src/sgml/version.sgmlMon Mar 18 18:04:11 2002 --- REL7_2/doc/src/sgml/version.sgml Thu May 10 21:46:33 2001 *** *** 3,7 documentation. In text, use for example version; to refer to them. -- ! !entity version 7.2.1 ! !entity majorversion 7.2.1 --- 3,7 documentation. In text, use for example version; to refer to them. -- ! !entity version 7.2 ! !entity majorversion 7.2 Is this right, or should majorversion still be 7.2? Right offhand the latter seems correct ... I wasn't sure what to do here. I figured if the docs were regenerated, it should say 7.2.1, and if they aren't, then they will stay as 7.2. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup.| Drexel Hill, Pennsylvania 19026 ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] Rolling v7.2.1 ...
Bruce Momjian writes: Is this right, or should majorversion still be 7.2? Right offhand the latter seems correct ... I wasn't sure what to do here. I figured if the docs were regenerated, it should say 7.2.1, and if they aren't, then they will stay as 7.2. But neither explanation warrants setting majorversion to 7.2.1. -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Rolling v7.2.1 ...
Peter Eisentraut wrote: Bruce Momjian writes: Is this right, or should majorversion still be 7.2? Right offhand the latter seems correct ... I wasn't sure what to do here. I figured if the docs were regenerated, it should say 7.2.1, and if they aren't, then they will stay as 7.2. But neither explanation warrants setting majorversion to 7.2.1. Why? Why shouldn't the documentation match the release number? -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup.| Drexel Hill, Pennsylvania 19026 ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Rolling v7.2.1 ...
Bruce Momjian [EMAIL PROTECTED] writes: But neither explanation warrants setting majorversion to 7.2.1. Why? Why shouldn't the documentation match the release number? Did you look at how majorversion is used? Setting it to 7.2.1 is *clearly* wrong. regards, tom lane ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Rolling v7.2.1 ...
Tom Lane wrote: Bruce Momjian [EMAIL PROTECTED] writes: But neither explanation warrants setting majorversion to 7.2.1. Why? Why shouldn't the documentation match the release number? Did you look at how majorversion is used? Setting it to 7.2.1 is *clearly* wrong. Oh, I see, there is majorversion and version. I put majorversion back to 7.2. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup.| Drexel Hill, Pennsylvania 19026 ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Rolling v7.2.1 ...
Bruce Momjian wrote: snip Why? Why shouldn't the documentation match the release number? Shouldn't major version still be 7.2, and version be 7.2.1. i.e. 7.2.1 is a minor release/update/subversion of 7.2? Regards and best wishes, Justin Clift -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup.| Drexel Hill, Pennsylvania 19026 ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org -- My grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to try to be in the first group; there was less competition there. - Indira Gandhi ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
