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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: TODO Item: ACL_CONNECT


  • From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
  • To: Gevik Babakhani <pgdev(at)xs4all(dot)nl>
  • Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
  • Subject: Re: TODO Item: ACL_CONNECT
  • Date: Tue, 25 Apr 2006 08:51:08 -0400
  • Message-id: <20060425125108(dot)GD24421(at)surnet(dot)cl>

Gevik Babakhani wrote:
> On Mon, 2006-04-24 at 23:16 -0400, Tom Lane wrote:
> > Why are we debating this?  It won't get accepted anyway, because the
> > whole thing is silly.  Show me one other object type that we issue
> > such warnings for, or anyone else who has even suggested that we should.

No other object type has the ability to require you to stop the server
and start a standalone backend to fix the mistake, which is what makes
this thing unique.


> So, I am very much confused. What do I do now. Do you mean the whole
> thing won't get accepted and I should stop developing the TODO item? or
> just strip the warning part.

Tom is referring to the WARNING.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group