Thread: Re: PostgreSQL-6.5.2-0.3 Comment

Re: PostgreSQL-6.5.2-0.3 Comment

From
"Oliver Elphick"
Date:
Chuan-kai Lin wrote: >I have recently installed your PostgreSQL 6.5.2-0.3 packages on my >newly upgraded potato system.
ODBC (which is the main purpose of >the upgrade to your packages) seems to be fine, though I am still >a little bit
pissedabout the dirty solution used to handle large >objects.  So far I have only encountered one problem: when I list
>alltables with \l under psql, psql disconnects itself from the >backend automatically.  Other operations, such as SQL
queries,seem >to work fine.  Any ideas?
 

There are no Debian-specific issues involved, so I am forwarding this
to the PostgreSQL interfaces list.  Perhaps someone will have some idea?


--      Vote against SPAM: http://www.politik-digital.de/spam/                ========================================
Oliver Elphick                                Oliver.Elphick@lfix.co.uk
Isle of Wight                              http://www.lfix.co.uk/oliver              PGP key from public servers; key
ID32B8FAA1                ========================================    "For the LORD God is a sun and shield; the LORD
will     give grace and glory; no good thing will he withhold      from them that walk uprightly."        Psalms 84:11





Re: [INTERFACES] Re: PostgreSQL-6.5.2-0.3 Comment

From
Thomas Lockhart
Date:
>   >I have recently installed your PostgreSQL 6.5.2-0.3 packages on my
>   >newly upgraded potato system.  ODBC (which is the main purpose of
>   >the upgrade to your packages) seems to be fine, though I am still
>   >a little bit pissed about the dirty solution used to handle large
>   >objects.  So far I have only encountered one problem: when I list
>   >all tables with \l under psql, psql disconnects itself from the
>   >backend automatically.  Other operations, such as SQL queries, seem
>   >to work fine.  Any ideas?
> There are no Debian-specific issues involved, so I am forwarding this
> to the PostgreSQL interfaces list.  Perhaps someone will have some idea?

Sure. Perhaps Mr. Lin would like to contribute a solution to whatever
is upsetting him regarding large objects.

Oh, that's not what you meant? ;)

\l (which lists databases, not tables) behaves itself on my RH5.2
system with the current development tree.
                  - Thomas

postgres=> \l
datname  |datdba|encoding|datpath  
---------+------+--------+---------
template1|   100|       0|template1
postgres |   100|       0|postgres 
(2 rows)

-- 
Thomas Lockhart                lockhart@alumni.caltech.edu
South Pasadena, California


Re: [INTERFACES] Re: PostgreSQL-6.5.2-0.3 Comment

From
Lamar Owen
Date:
Thomas Lockhart wrote:
> \l (which lists databases, not tables) behaves itself on my RH5.2
> system with the current development tree.

In the interests of thoroughness, I did the following:
I took my production system (running the 6.5.1-0.7lo RPM's), and tried
\l, which worked fine.  I then upgraded to the 6.5.2-1 RPM's, and tried
\l -- and it works fine.

System is Mandrake 5.3 (linux kernel 2.0.36, glibc 2.0.7).  I'll try it
against my RedHat 6.1 partition after I reboot into it here in a moment
(it's on this very notebook).

--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11


Re: [INTERFACES] Re: PostgreSQL-6.5.2-0.3 Comment

From
"Oliver Elphick"
Date:
Lamar Owen wrote: >Thomas Lockhart wrote: >> \l (which lists databases, not tables) behaves itself on my RH5.2 >>
systemwith the current development tree. > >In the interests of thoroughness, I did the following: >I took my
productionsystem (running the 6.5.1-0.7lo RPM's), and tried >\l, which worked fine.  I then upgraded to the 6.5.2-1
RPM's,and tried >\l -- and it works fine. > >System is Mandrake 5.3 (linux kernel 2.0.36, glibc 2.0.7).  I'll try it
>againstmy RedHat 6.1 partition after I reboot into it here in a moment >(it's on this very notebook).
 
And that's the result I get with Debian 6.5.2-2 - no problem found.  So I conclude
that it's something wrong in your database.

Try doing `select * from pg_database;' (which does the same as \l) and see
what results you get.  Turn on backend debugging and logging and see what the
error is.

(I was confused by the mention of odbc; this problem doesn't have anything to
do with odbc, does it?)

--      Vote against SPAM: http://www.politik-digital.de/spam/                ========================================
Oliver Elphick                                Oliver.Elphick@lfix.co.uk
Isle of Wight                              http://www.lfix.co.uk/oliver              PGP key from public servers; key
ID32B8FAA1                ========================================    "For the LORD God is a sun and shield; the LORD
will     give grace and glory; no good thing will he withhold      from them that walk uprightly."        Psalms 84:11