Trying to remove "superuser" from a role causes a confirmation message.
That's fine. The problem is that after user click either "ok" or
"cancel" have same effect: the "superuser" is marked again, no matter what.
The only way to remove "superuser" is by issueing the SQL command.
Regards,
Edson
Trying to remove "superuser" from a role causes a confirmation message.
That's fine. The problem is that after user click either "ok" or
"cancel" have same effect: the "superuser" is marked again, no matter what.
The only way to remove "superuser" is by issueing the SQL command.
Regards,
Edson
Hi All,
Sorry if this has come up before but one of the more irritating features
of pgAdmin for me has been this little bit of behavior (on Mac OS X):
1) Select a database
2) right click select properties...
3) click in the name field
4) use forward delete to delete the next character
I get a ni
Nevermind - the reason I couldn't reproduce the issue is that it's
already fixed. I must have spotted it while I was working on this
change:
http://git.postgresql.org/gitweb/?p=pgadmin3.git;a=commit;h=7b20a39c7f018c12901e15cc23bb827517242bd1
So, the problem will be resolved in 1.16.2.
On Thu, Fe
On Thu, Feb 7, 2013 at 9:34 AM, Vjacheslav A. wrote:
> Here is log.
Thanks. Like another I was sent offlist, it looks fine. Can you please
run "SELECT * FROM pg_shdescription", and tell me if you see the
comment you added in there?
Thanks.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter:
On Thu, Feb 7, 2013 at 12:30 PM, Michal Kozusznik
wrote:
>
>> That's basically what the patch I posted does. The problem is that the
>> base class doesn't have any knowledge of what controls are on an
>> instantiated dialogue, or how to test if they've been changed from
>> whatever the default is
That's basically what the patch I posted does. The problem is that the
base class doesn't have any knowledge of what controls are on an
instantiated dialogue, or how to test if they've been changed from
whatever the default is (for new objects) or from whatever pgObject
derived object exists for
Success.
One must go into the configuration in pgAdmin (Tools menu, Server
Configuration) and *enable* the shared_preload_libraries item by checking
the checkbox next to it, save the config, and then stop/restart the
database service.
Tim
On Thu, Feb 7, 2013 at 5:38 AM, Tim Romano wrote:
> Th
Hi
On Thu, Feb 7, 2013 at 10:38 AM, Tim Romano wrote:
> Thanks for taking time to reply, Dave. I have stopped and restarted the
> service several times, and have opened and closed pgAdmin several times.
> It's definitely a PL/pgsql function. That's all I've been writing. language
> plpgsql
>
> D
On Thu, Feb 7, 2013 at 10:57 AM, Michal Kozusznik
wrote:
> OK. Thanx for deeper explanation. Looks like I missed a point twice :)
>
>
>> If you have a simple way to make it work, I'd love
>> to see a proposed patch because at the moment, I don't see a way to do
>> it that wouldn't take at least a
OK. Thanx for deeper explanation. Looks like I missed a point twice :)
If you have a simple way to make it work, I'd love
to see a proposed patch because at the moment, I don't see a way to do
it that wouldn't take at least a few days of work.
Don't know architecture of pgadmin, but if reques
Thanks for taking time to reply, Dave. I have stopped and restarted the
service several times, and have opened and closed pgAdmin several times.
It's definitely a PL/pgsql function. That's all I've been writing.
language plpgsql
Does the debugger definitely work on Windows 7 64-bit version?
Wh
On Thu, Feb 7, 2013 at 10:20 AM, Michal Kozusznik
wrote:
> On 6.2.2013 18:19, Dave Page wrote:
>>
>> It won't be fixed in 1.16.2 I doubt, as it's a change in behaviour
>> that's been established for over 10 years with no previous complaints
>> that I can recall.
>
>
> I don't want to be rude, but
On 6.2.2013 18:19, Dave Page wrote:
It won't be fixed in 1.16.2 I doubt, as it's a change in behaviour
that's been established for over 10 years with no previous complaints
that I can recall.
I don't want to be rude, but maybe no one has used this feature due bugs
appearing from time to time.
[re-adding the list]
On Wed, Feb 6, 2013 at 10:41 PM, Bastiaan Olij wrote:
> Hey Dave,
>
> As you've read from David's reply the job's status now comes back as
> successful which solves our immediate issue. I did a little more testing
> to see if I could get it to react to different exit codes an
On Wed, Feb 6, 2013 at 7:58 PM, Tim Romano wrote:
> I followed the steps to enable the debugger:
>
> 1. Modified the postgresql.conf file as directed shared_preload_libraries =
> '$libdir/plugin_debugger.dll'
> 2. Stopped and restarted the database service.
> 3. Ran CREATE EXTENSION pldbgapi in th
16 matches
Mail list logo
