From: | Erwin Brandstetter <brandstetter(at)falter(dot)at> |
---|---|
To: | guillaume(at)lelarge(dot)info |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: Redundant statements |
Date: | 2010-04-29 22:35:37 |
Message-ID: | 4BDA09B9.2060904@falter.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On 29.04.2010 18:48, guillaume(at)lelarge(dot)info wrote:
> Le 29/04/2010 17:50, Guillaume Lelarge a écrit :
>
>> Le 29/04/2010 17:28, Erwin Brandstetter a écrit :
>>
>>> On 29.04.2010 15:21, guillaume(at)lelarge(dot)info wrote:
>>>
>> [...]
>>
>>>>> What do you think of it? Should I create a ticket?
>>>>>
>>>>>
>>>> Well, I would like to have a better handling of the "SET STORAGE"
>>>> statement. So, yes, you can create a ticket on that, without being too
>>>> specific on the solution, which still needs some talk.
>>>>
>>>>
>>> So we agree on "SET STORAGE". I'll create a ticket on that.
>>>
>>>
>> Yeah. I also found how to detect the "initial" value of the storage
>> (column typstorage in pg_catalog.pg_type). So I'll work on this right now.
>>
>>
> Fixed. I can provide you a new pgAdmin3.exe quite easily if you want.
>
Cool. If you provide me with a new pgAdmin3.exe I will use it for tests.
We are moving in on a point release v1.10.3, aren't we? I found 21
resolved bugs tagged "1.10.3" in trac - compared to 9 for v1.10.2. So we
might call it early alpha-testing?
Regards
Erwin
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2010-04-29 22:40:58 | Re: Redundant statements |
Previous Message | pgAdmin Trac | 2010-04-29 22:35:23 | Re: [pgAdmin III] #14: Save graphical explain output |