Re: CREATE DATABASE command in Extended Query mode of 3.0

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Carlos Guzman Alvarez <carlosga(at)telefonica(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: CREATE DATABASE command in Extended Query mode of 3.0
Date: 2003-07-09 15:35:37
Message-ID: 1081.1057764937@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Carlos Guzman Alvarez <carlosga(at)telefonica(dot)net> writes:
> Hello:
>>> No, it should just work. Can you give a test case? Do you see similar
>>> problems with other utility commands, or is it only CREATE DATABASE?

> I have made a litlle test more and i have it working now, i have made
> change for send a Sync message instead of a Flush message after execute
> the command and now seems to be working as expected, is this correct or
> it needs to work with the Flush too??

You do need to use Sync rather than Flush to create transaction
boundaries and error restart points. I suspect your problem was coming
from having only a Flush and not a Sync between the CREATE DATABASE and
the *prior* command.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 2003-07-09 15:55:18 Re: PlPython
Previous Message Rod Taylor 2003-07-09 13:26:28 Re: sugsestions