On Tue, 2011-11-01 at 16:11 +1100, Evan Martin wrote:
> Hi,
>
> I'm using pgAdmin 1.14.0 on Windows 7 x64 with PostgreSQL 9.1.1. As part
> of developing my application I regularly drop and re-create the entire
> schema containing my DB objects. The behaviour of pgAdmin when this
> happens is co
On Sun, 2011-10-30 at 07:46 +0100, pasman pasmaĆski wrote:
> Hi.
> Extensions load sometimes big number of functions.
> I think that they should be displayed as gray.
>
That won't lower the number of functions :)
But, yes, we could probably display the functions' extensions another
way. Another
On Mon, 2011-10-31 at 11:08 +0100, jan-peter.seif...@gmx.de wrote:
> Hello,
>
> unfortunately this issue isn't resolved yet.
>
> If I dump a database on a ( local ) PostgreSQL 8.4 ( 32-bit ) server using
> pgAdmin 1.12 and later I get massive blinking and the whole system ( Windows
> 64-bit ) s
On Mon, 2011-10-31 at 18:26 -0300, Fernando Hevia wrote:
> [...]
> I could reproduce the issue in a fresh Windows 7 install with no other apps
> running other than pgAdmin v1.14.0.
> From what I could see, the execute-to-file function runs in 2 stages:
> 1. Rows are retrieved from DB server to RAM
Hi,
I'm using pgAdmin 1.14.0 on Windows 7 x64 with PostgreSQL 9.1.1. As part
of developing my application I regularly drop and re-create the entire
schema containing my DB objects. The behaviour of pgAdmin when this
happens is confusing to the user and doesn't allow easy recovery:
1) If I ex