On 08/03/2015 09:51, Dave Page wrote:
> I don't check regularly, but I did just take a look and the
> instructions are there and do take you to a page with options to
> unsubscribe.
>
> Further, both the PostgreSQL (http://www.postgresql.org/list/) and
> pgAdmin websites (http://www.pgadmin.org/su
2015-03-08 12:51 GMT+01:00 Danilo Fortunato :
> Thanks Guillaume.
> On which version of PostegreSQL have you done the test ?
>
>
9.4. Kinda like a reflex to always use the latest :)
Should have tried the 8.2, sorry.
> If your test, as I suppose, has been done on a version of PostgreSQL more
>
Thanks Guillaume.
On which version of PostegreSQL have you done the test ?
If your test, as I suppose, has been done on a version of PostgreSQL
more recent than 8.2.15, than this bug could only arise with older
versions of PostgreSQL, and it have already been fixed (I found several
references
2015-03-08 10:51 GMT+01:00 Dave Page :
> I don't check regularly, but I did just take a look and the instructions
> are there and do take you to a page with options to unsubscribe.
>
>
Works for me too.
> Further, both the PostgreSQL (http://www.postgresql.org/list/) and
> pgAdmin websites (http
I don't check regularly, but I did just take a look and the instructions are
there and do take you to a page with options to unsubscribe.
Further, both the PostgreSQL (http://www.postgresql.org/list/) and pgAdmin
websites (http://www.pgadmin.org/support/list.php) explain how to unsubscribe -
gi
Hi,
2015-03-07 22:01 GMT+01:00 Danilo Fortunato :
> I use pgAdmin III 1.20.0 on a Greenplum database 4.2.6.3, which is based
> on PostgreSQL 8.2.15.
> I'm aware that this version of PostgreSQL is no more supported by pgAdmin.
>
> I noticed that the DDL scripts generated by pgAdmin for the tables,
