Skip site navigation (1) Skip section navigation (2)

Re: Cygwin PostgreSQL postmaster abort problem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jason Tishler <Jason(dot)Tishler(at)dothill(dot)com>
Cc: pgsql-ports(at)postgresql(dot)org
Subject: Re: Cygwin PostgreSQL postmaster abort problem
Date: 2000-12-31 03:56:43
Message-ID: 6340.978235003@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-ports
Jason Tishler <Jason(dot)Tishler(at)dothill(dot)com> writes:
> --- postgresql-20001229.orig/src/backend/utils/mmgr/mcxt.c	Tue Aug 22 03:00:13 2000
> +++ postgresql-20001229/src/backend/utils/mmgr/mcxt.c	Fri Dec 29 23:46:31 2000
> @@ -45,7 +45,7 @@ MemoryContext PostmasterContext = NULL;
>  MemoryContext CacheMemoryContext = NULL;
>  MemoryContext QueryContext = NULL;
>  MemoryContext TopTransactionContext = NULL;
> -MemoryContext TransactionCommandContext = NULL;
> +DLLIMPORT MemoryContext TransactionCommandContext = NULL;

These changes look fine as far as they go, but if you think
TransactionCommandContext needs to be DLLIMPORT, why not the other
global context variables, too?  What led you to mark it DLLIMPORT
anyway?

			regards, tom lane

In response to

Responses

pgsql-ports by date

Next:From: Jason TishlerDate: 2000-12-31 05:12:18
Subject: Re: Cygwin PostgreSQL postmaster abort problem
Previous:From: Jason TishlerDate: 2000-12-31 03:48:53
Subject: Re: Cygwin PostgreSQL postmaster abort problem

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group