On Thu, 2011-07-07 at 14:57 +0200, Durumdara wrote:
> Hi!
>
> Thank you very much! I everytime forget to check new version.
>
> You could do some "check new version on internet" function.
> This can run once per week. :-)
>
Yeah, that's something I would like to have. I know how to do most of
t
Hi!
Thank you very much! I everytime forget to check new version.
You could do some "check new version on internet" function.
This can run once per week. :-)
Thanks:
dd
2011/7/7 Guillaume Lelarge :
> On Thu, 2011-07-07 at 09:22 +0200, Durumdara wrote:
>> Hi!
>>
>> I'm very-very thanks for it
On Thu, 2011-07-07 at 09:22 +0200, Durumdara wrote:
> Hi!
>
> I'm very-very thanks for it!
> I was so tired yesterday, and I don't clicked on any connections, so
> the buttons were greyed, and I could not see that there are buttons.
> :-)
>
> Client "start" column is too short. May you can save t
Hi!
I'm very-very thanks for it!
I was so tired yesterday, and I don't clicked on any connections, so
the buttons were greyed, and I could not see that there are buttons.
:-)
Client "start" column is too short. May you can save the columns width
to preserve the good size.
Thanks and regards:
On Wed, 2011-07-06 at 16:09 +0200, Durumdara wrote:
> Dear Author!
>
> I need to know that which ways I have to abort a runaway query/stored
> procedure.
>
> As I saw, pgAdmin CAN abourt my own queries.
> It is ok.
>
> But what's happens when:
> - somebody (not me) started a query that have too
Dear Author!
I need to know that which ways I have to abort a runaway query/stored procedure.
As I saw, pgAdmin CAN abourt my own queries.
It is ok.
But what's happens when:
- somebody (not me) started a query that have too less filter, and
becomes unlimited
- I started a query or stored proc wh
