Re: [HACKERS] [PATCHES] Fix for running from admin account on win32

You'll still need to run the postmaster frmo pg_ctl to get the run as admin part. The only part that could be moved is the Job Object for management. And you're normally not going to need that one when you're not running as a service. Maybe sometimes, but I doubt it's

Re: [PATCHES] drop if exists remainder

Andrew Dunstan [EMAIL PROTECTED] writes: Here's a first draft patch for DROP ... IF EXISTS for the remaining cases, namely: LANGUAGE, TABLESPACE, TRIGGER OPERATOR CLASS, FUNCTION, AGGREGATE, OPERATOR, CAST and RULE. At what point does this stop being useful and become mere bloat? The only

Re: [PATCHES] drop if exists remainder

Tom Lane wrote: Andrew Dunstan [EMAIL PROTECTED] writes: Here's a first draft patch for DROP ... IF EXISTS for the remaining cases, namely: LANGUAGE, TABLESPACE, TRIGGER OPERATOR CLASS, FUNCTION, AGGREGATE, OPERATOR, CAST and RULE. At what point does this stop being useful and

Re: [PATCHES] TODO-Item: TRUNCATE ... CASCADE

On Fri, Feb 03, 2006 at 10:27:30AM -0500, Tom Lane wrote: Basically: it's the user's fault if he says TRUNCATE t2 in a situation where the referent of t2 might be changing concurrently. But once you've identified t2, it's your fault if you don't track the dependencies of t2 correctly, even if

Re: [PATCHES] drop if exists remainder

Andrew Dunstan wrote: Tom Lane wrote: Andrew Dunstan [EMAIL PROTECTED] writes: Here's a first draft patch for DROP ... IF EXISTS for the remaining cases, namely: LANGUAGE, TABLESPACE, TRIGGER OPERATOR CLASS, FUNCTION, AGGREGATE, OPERATOR, CAST and RULE. At what point

Re: [PATCHES] drop if exists remainder

Bruce Momjian wrote: However, I see CREATE ROLE doesn't have REPLACE functionality, so what is the logic of when we need IF EXISTS and when we don't? Perhaps they all should have it, and the REPLACE is just for objects you want to replace but keep existing linkage in place. That was my

Re: [PATCHES] pg_restore COPY error handling

Stephen Frost [EMAIL PROTECTED] writes: I believe the attached patch does this now. Under my test case it correctly handled things. I'm certainly happier with it this way and apologize for not realizing this better approach sooner. Please comment. Applied (with trivial stylistic changes)

Re: [PATCHES] pg_restore COPY error handling

* Tom Lane ([EMAIL PROTECTED]) wrote: Stephen Frost [EMAIL PROTECTED] writes: I believe the attached patch does this now. Under my test case it correctly handled things. I'm certainly happier with it this way and apologize for not realizing this better approach sooner. Please comment.