DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding;
	b=EUUxJ/qvgLQcJ0sy/3qCTaGNCgTl0Q4IlIUTia9fzaOWRc6wwKrhvnMeanuznyaDQ7pQMhApCIlfWgED4B6WYZSyG38pcUVmeu4awTjKaFB32AiA/Saw6Z20exJSrokVtXWMW9WX2CIAWhftZCSpo+GKbPwiAgFulKn5sNUYwTM=
Message-ID: <6c21003b050226125634e9964@mail.gmail.com>
Date: Sat, 26 Feb 2005 14:56:52 -0600
From: Don Drake <dondrake@gmail.com>
Reply-To: Don Drake <dondrake@gmail.com>
To: pgsql-sql@postgresql.org
Subject: AutoCommit and DDL
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

I have a generic function that creates partition tables and their
corresponding indexes and constraints.

I've tested the function using a GUI and it works great.  We
implemented in our data loaders (written in perl) and the DB
connections have AutoCommit turned off.  When we run it in the perl
script, I see the code being execute to create the tables, etc. but
they are never created, even with a commit at the end.  It appears
something is causing the table creation to get rolled back.

I turned AutoCommit on and re-ran the perl script and the tables get
created.  Why won't these table's get created when AutoCommit is off? 
Why do I have to commit DDL?

I'm running 7.4.3.

Thanks.

-Don

-- 
Donald Drake
President
Drake Consulting
http://www.drakeconsult.com/
http://www.MailLaunder.com/
312-560-1574