[HACKERS] Re: Interesting failure mode for initdb
Tom Lane writes: > I think one part of the fix is to modify elog() so that a FATAL exit > results in exit status 1, not 0, if not IsUnderPostmaster. Right. > At the very least we should hack initdb so that --debug removes > "-o /dev/null" from PGSQL_OPT, but can you see any way to provide > filtered stderr output from the backend in the normal mode of operation? I've removed some of the >/dev/null's and the only undesired output I get is of this form: Enabling unlimited row width for system tables. POSTGRES backend interactive interface $Revision: 1.208 $ $Date: 2001/02/24 02:04:51 $ backend> backend> POSTGRES backend interactive interface $Revision: 1.208 $ $Date: 2001/02/24 02:04:51 $ backend> backend> Creating system views. POSTGRES backend interactive interface $Revision: 1.208 $ $Date: 2001/02/24 02:04:51 $ ISTM that the backend shouldn't print a prompt when it's non-interactive. Then maybe we don't need to filter the output at all. -- Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/ ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
[HACKERS] Re: Interesting failure mode for initdb
Peter Eisentraut <[EMAIL PROTECTED]> writes: > I've removed some of the >/dev/null's and the only undesired output I get > is of this form: > POSTGRES backend interactive interface > $Revision: 1.208 $ $Date: 2001/02/24 02:04:51 $ > backend> backend> > POSTGRES backend interactive interface > $Revision: 1.208 $ $Date: 2001/02/24 02:04:51 $ That stuff comes out on stdout; all of the interesting stuff is on stderr. I don't have a problem with routing stdout to /dev/null. > ISTM that the backend shouldn't print a prompt when it's non-interactive. More trouble than it's worth, I think ... regards, tom lane ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[HACKERS] Re: Interesting failure mode for initdb
I said: > That stuff comes out on stdout; all of the interesting stuff is on > stderr. Actually, given the -o option all of the interesting stuff will go to wherever -o says. At this stage of the release cycle I suppose we must resist the temptation to define -o '|command' as doing a popen(), but maybe for 7.2 something could be done with "-o '|grep -v ^DEBUG'" ... 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: AW: AW: AW: [HACKERS] WAL does not recover gracefully from ou t-of -dis k-sp ace
Denis Perchine <[EMAIL PROTECTED]> writes: > On Saturday 10 March 2001 08:41, Tom Lane wrote: >> More numbers, these from a Powerbook G3 laptop running Linux 2.2: > Eeegghhh. Sorry... But where did you get O_DSYNC on Linux? > bits/fcntl.h: # define O_DSYNC O_SYNC Hm, must be. Okay, so those two sets of numbers should be taken as fsync() and O_SYNC respectively. Still the conclusion seems pretty clear: the open() options are way more efficient than calling fsync() separately. regards, tom lane ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
[HACKERS] doxygen & PG
Is this page http://members.fortunecity.com/nymia/postgres/dox/backend/html/ common knowledge? It appears to be an automatically-generated cross-reference documentation web site. My impression is that appropriately-marked comments in the code get extracted to the web pages, too, so it is also a way to automate internal documentation. Nathan Myers [EMAIL PROTECTED] ---(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] doxygen & PG
[EMAIL PROTECTED] (Nathan Myers) writes: > Is this page > http://members.fortunecity.com/nymia/postgres/dox/backend/html/ > common knowledge? Interesting, but bizarrely incomplete. (Yeah, we have only ~100 struct types ... sure ...) regards, tom lane ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] doxygen & PG
On Sat, Mar 10, 2001 at 06:29:37PM -0500, Tom Lane wrote: > [EMAIL PROTECTED] (Nathan Myers) writes: > > Is this page > > http://members.fortunecity.com/nymia/postgres/dox/backend/html/ > > common knowledge? > > Interesting, but bizarrely incomplete. (Yeah, we have only ~100 > struct types ... sure ...) It does say "version 0.0.1". What was interesting to me is that the interface seems a lot more helpful than the current CVS web gateway. If it were to be completed, and could be kept up to date automatically, something like it could be very useful. Nathan Myers [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
Re: [HACKERS] doxygen & PG
The site mentioned was created by me. I used doxygen to create those html files. And it's just the first stab. It doesn't have have doxygen tags yet that's why it looks like that. The reason why I made it was to make it easier for me ( and others as well ) to read the code though. So far, I've learned a lot using this technique. There is another one I'm working on and it's at http://members.fortunecity.com/nymia/vsta/boot_layout.html - Original Message - From: Nathan Myers <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, March 10, 2001 3:48 PM Subject: Re: [HACKERS] doxygen & PG > On Sat, Mar 10, 2001 at 06:29:37PM -0500, Tom Lane wrote: > > [EMAIL PROTECTED] (Nathan Myers) writes: > > > Is this page > > > http://members.fortunecity.com/nymia/postgres/dox/backend/html/ > > > common knowledge? > > > > Interesting, but bizarrely incomplete. (Yeah, we have only ~100 > > struct types ... sure ...) > > It does say "version 0.0.1". > > What was interesting to me is that the interface seems a lot more > helpful than the current CVS web gateway. If it were to be completed, > and could be kept up to date automatically, something like it could > be very useful. > > Nathan Myers > [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 > ---(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] Do we still need PowerPC-specific timestamp_is_current/epoch?
At the end of backend/utils/adt/datetime.c, there is some fairly ugly code that is conditionally compiled on #if defined(linux) && defined(__powerpc__) Do we still need this? The standard versions of TIMESTAMP_IS_CURRENT and TIMESTAMP_IS_EPOCH appear to work just fine on my Powerbook G3 running Linux 2.2.18 (LinuxPPC 2000 Q4 distro). I see from the CVS logs that Tatsuo originally introduced this code on 1997/07/29 (at the time it lived in dt.c and was called datetime_is_current & datetime_is_epoch). I suppose that it must have been meant to work around some bug in old versions of gcc for PPC. But it seems to me to be a net decrease in portability --- it's assuming that the symbolic constants DBL_MIN and -DBL_MIN will produce particular bit patterns --- so I'd like to remove it unless someone knows of a recent Linux/PPC release that still needs it. regards, tom lane ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] Do we still need PowerPC-specifictimestamp_is_current/epoch?
> At the end of backend/utils/adt/datetime.c, there is some fairly ugly > code that is conditionally compiled on > > #if defined(linux) && defined(__powerpc__) > > Do we still need this? The standard versions of TIMESTAMP_IS_CURRENT > and TIMESTAMP_IS_EPOCH appear to work just fine on my Powerbook G3 > running Linux 2.2.18 (LinuxPPC 2000 Q4 distro). > > I see from the CVS logs that Tatsuo originally introduced this code > on 1997/07/29 (at the time it lived in dt.c and was called > datetime_is_current & datetime_is_epoch). I suppose that it must have > been meant to work around some bug in old versions of gcc for PPC. Yes. > But it seems to me to be a net decrease in portability --- it's assuming > that the symbolic constants DBL_MIN and -DBL_MIN will produce particular > bit patterns --- so I'd like to remove it unless someone knows of a > recent Linux/PPC release that still needs it. Let me check if my Linux/PPC still needs the workaround. BTW, what about MkLinux? Anybody tried recent DR5 release? -- Tatsuo Ishii ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: AW: AW: AW: [HACKERS] WAL does not recover gracefully from ou t-of -dis k-sp ace
> > Ok, I've made changes in xlog.c and run tests: > > Could you send me your diffs? Sorry, Monday only. Vadim ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
