The connection to the database is dropped occasionally (as far as I can
tell, independently of internet connectivity issues). I have experienced
this quite a lot. I do not think it is PgAdmin that drops the connection.
Could be postgres itself is dropping the connection.
There have been a number
On Tue, Oct 13, 2009 at 6:59 PM, John wrote:
> Hi,
> I have a fellow assocate that uses pgAdmin3 remotely (he is in GA the DB is in
> CA). He insists that a "time out" is somewhere in pgAdmin. He loses
> connection often. It has happen while are talking on Skype, or not talking
> on Skype. It'
Le mardi 13 octobre 2009 à 19:59:04, John a écrit :
> Hi,
> I have a fellow assocate that uses pgAdmin3 remotely (he is in GA the DB is
> in CA). He insists that a "time out" is somewhere in pgAdmin. He loses
> connection often. It has happen while are talking on Skype, or not
> talking on Sk
Hi,
I have a fellow assocate that uses pgAdmin3 remotely (he is in GA the DB is in
CA). He insists that a "time out" is somewhere in pgAdmin. He loses
connection often. It has happen while are talking on Skype, or not talking
on Skype. It's also has happened while I was remotely connected.
>> ALTER SEQUENCE ... OWNER TO ...;
>> GRANT ... ON SEQUENCE ... TO ...;
>> ...
>>
>
>I don't quite understand why it should be your way and not the other. Care
>to
>explain?
>
>Regards.
>
>
>--
>Guillaume.
Oops, sorry, there is no syntax ALTER SEQUENCE ... OWNER TO ...;
But since release 8.2,
Hello, Dave
If it is possible - you can change directory names. Lets say instead of
having directory v1.0.1 you could have v1.00.01. Of course if other web
pages have links of these directories - it is hardly an option
I think the newest version should be at the top or at the bottom of the
On Tue, Oct 13, 2009 at 8:12 AM, Julius Tuskenis wrote:
> Hello,
>
> I think what causes confusion is the way versions are ordered in releases
> list (http://www.postgresql.org/ftp/pgadmin3/release/). Version 1.10 goes
> after 1.0 (not after 1.8 as many expects). I assume the ordering is done
> au
On Mon, Oct 5, 2009 at 12:48 PM, Dmitry Samokhin wrote:
> To implement this in case of empty, but not null, ACL of functions (and
> other database objects granting default access to PUBLIC), the
> reverse-engineering procedure of pgAdmin might be modified for the script to
> look like:
>
> CREATE
Hello,
I think what causes confusion is the way versions are ordered in
releases list (http://www.postgresql.org/ftp/pgadmin3/release/). Version
1.10 goes after 1.0 (not after 1.8 as many expects). I assume the
ordering is done automatically, but it would be much better to tweak it
a bit and
On Tue, Oct 13, 2009 at 9:08 AM, Julius Tuskenis wrote:
> Hello, Dave
>
> If it is possible - you can change directory names. Lets say instead of
> having directory v1.0.1 you could have v1.00.01. Of course if other web
> pages have links of these directories - it is hardly an option
> I thin
10 matches
Mail list logo
