> > 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]
> 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 Powerb
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
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 le
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 ..
[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
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 a
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
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(), bu
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
> $R
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
> fil
11 matches
Mail list logo