On Sat, Apr 22, 2006 at 14:20:32 -0700,
daveg <[EMAIL PROTECTED]> wrote:
> On Sat, Apr 22, 2006 at 01:49:25PM -0700, David Fetter wrote:
> > On Sat, Apr 22, 2006 at 01:14:42PM -0700, David Gould wrote:
> >
> > > To avoid running out of swap and triggering the oom killer we have
> > > had to redu
In this email
http://archives.postgresql.org/pgsql-bugs/2006-03/msg00076.php
belonging to bug #2310, Tom says
> I wrote:
> > The relevant owner field for a composite type is pg_type.typowner.
> > We don't bother to maintain pg_class.relowner for the subsidiary
> > pg_class entry.
>
> Actua
I am not happy with my patch and am going to try a more comprehensive
restructuring --- will post later.
---
Bruce Momjian wrote:
> Tom Lane wrote:
> > Bruce Momjian writes:
> > > Tom Lane wrote:
> > >> The patch as given s
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
> *) Change where NaN is generated. Using 0.0/0.0 doesn't work in VC++
> because it detects it as a divide-by-zero at the compile stage.
If they're going to be that anally uncooperative, why don't they have
the required-by-C99-spec macro for NAN? Or a
""Magnus Hagander"" <[EMAIL PROTECTED]> wrote
> I've been working on getting the full backend to compile and run using
> Visual C++ instead of mingw/gcc, and have made some good progress.
>
This is great!
> *) Add s_lock implementation based on InterlockedCompareExchange instead
> of assembly co
Here is an updated patch. I broke out the statement_timestamp and
statement_timeout handling into separate functions, initialize_command()
and finalize_command(), which call the xact start/stop internally.
This clears up the API because now start/stop xact can be called
independent of the statem
