Dear pgadmin support community members,
I need your help for some tricky problem that I was unable to solve.
I am using pgadmin under Mac OS X Panther (10.3.9).
The newest pgadmin releases only support Tiger (10.4) since they are
compiled with dynamic links against 10.4 libraries and frameworks
2007/1/18, Dave Page <[EMAIL PROTECTED]>:
> --- Original Message ---
> From: Laurent ROCHE <[EMAIL PROTECTED]>
> To: pgadmin-support@postgresql.org
> Sent: 1/18/07, 7:21:35 PM
> Subject: [pgadmin-support] Crash and sending report !
>
> Hi,
>
> When ever there's a crash (it's about every
> --- Original Message ---
> From: Laurent ROCHE <[EMAIL PROTECTED]>
> To: pgadmin-support@postgresql.org
> Sent: 1/18/07, 7:21:35 PM
> Subject: [pgadmin-support] Crash and sending report !
>
> Hi,
>
> When ever there's a crash (it's about every other time ... when I close PG
> Admin .
Devrim GUNDUZ wrote:
Hi,
On Mon, 2007-01-15 at 21:53 -0500, William McCoy wrote:
I have noticed that the rpm of pgadmin3 v. 1.6.1 on the PostgreSQL
download site is the same file as the pgadmin3-docs rpm file. In
fact,
they are both the pgadmin3-docs-1.6.1-2.i386.rpm file. That is, the
file c
Hi,
When ever there's a crash (it's about every other time ... when I close PG
Admin ... so no big deal ;-) !) is it worth me sending the report to Microsoft ?
Does it get to the PG Admin people in the end ?
Cheers,
[EMAIL PROTECTED]
The Computing Froggy
Joris Dobbelsteen wrote:
> I have the feeling this could be caused by pgAdmin because it is caching
> information. Perhaps that a refresh of the database is a workarround.
>
> Unfortunally I'm no expert and I'm not sure about this.
You should refresh the table node following vacuum and check th
I have the feeling this could be caused by pgAdmin because it is caching
information. Perhaps that a refresh of the database is a workarround.
Unfortunally I'm no expert and I'm not sure about this.
- Joris
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] On Beh
Hi,
I am working on an import of databases, so I keep dropping and re-creating
schemas, and then populating tables.
Even, if I do a VACUUM ANALYSE on the entire DB, PG Admin will prompt me to
perform a VACUUM when I use one of the tables populated.
Is this normal ?
I would have thought that con
