Hi,
On Thu, 9 Mar 2006, Marian POPESCU wrote:
Is Fedora Core forgotten?
When is expected the release 1.4.2 for FC4?
Sorry for the delay. I have some health problems. I'll try to build the
packages on Monday.
Regards,
--
The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
Postgre
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Crowson,
Sarah J Ms (Contractor) Northrop GrummanSent: 10 March 2006
19:07To: pgadmin-support@postgresql.orgSubject:
[pgadmin-support] on Server Status (Status)
window (UNCLASSIFIED)
Classification:
At current time "InitPlan" display as last part
of explain diagram.
See below sample output for check incorrect diagram
Limit (cost=9.86..180.39 rows=22 width=55)
InitPlan
-> Index Scan using pw_ux on pw (cost=0.00..4.93 rows=1 width=4)
Index Cond: (wr = '30'
Classification: UNCLASSIFIED
Caveats: NONE
Hello,
I have been running my head into the wall trying to figure
out where this is coming from to fix it. I am running on a Red Hat Enterprise
4 Update 2 server with Postgres 8.1.2, wxWidgets 2.6.2, and pgadmin 1.4.1. I
did load the admin
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of David Nash
> Sent: 10 March 2006 14:02
> To: pgadmin-support@postgresql.org
> Subject: Re: [pgadmin-support] Edit grid crashes adding new
> rows to table with autoincrement primary key.
>
> >> Inte
>> Interesting. Out of interest (if you still have it), what does pg_dump
>> think the schema looks like? It sounds like pgAdmin is misreading the
>> schema somehow, causing the crash - most likely when it tries to detect
>> the primary key. One thought - in the edit grid, did the int8 column
>> ha
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of David Nash
> Sent: 10 March 2006 13:18
> To: pgadmin-support@postgresql.org
> Subject: Re: [pgadmin-support] Edit grid crashes adding new
> rows to table with autoincrement primary key.
>
> Dave, y
Dave, your suggestion worked ... creating a new database, and a new table
within it made it possible to edit the table without error. For
completeness, the new table definition appears below, but it's pretty clear
that there's no meaningful difference between it and the one that didn't
work:
CREA
