Thread: Buncho-Text during commands.

H-

Well I have been able to get the lastest postgres up and running on the
system. Yeah!! 8^)

I do have a concern though.

Every command I put into the database dumps a whole bunch of text and
then the answer.
For example:

template1=# \l
001208.15:25:43.529  [2824] StartTransactionCommand
001208.15:25:43.529  [2824] query: SELECT pg_database.datname as
"Database",
       pg_user.usename as "Owner",
       pg_encoding_to_char(pg_database.encoding) as "Encoding"FROM
pg_database, pg_user
WHERE pg_database.datdba = pg_user.usesysid

UNION

SELECT pg_database.datname as "Database",
       NULL as "Owner",
       pg_encoding_to_char(pg_database.encoding) as "Encoding"FROM
pg_database
WHERE pg_database.datdba NOT IN (SELECT usesysid FROM pg_user)
ORDER BY "Database"
001208.15:25:43.537  [2824] ProcessQuery
001208.15:25:43.539  [2824] CommitTransactionCommand
        List of databases
 Database  |  Owner   | Encoding
-----------+----------+-----------
 template1 | postgres | SQL_ASCII

This use to not do this.
Is there a way to put all this stuff in the background? Or is this
installation not working correctly?

Thanks for any info you might have.
-Sterling

On 8 Dec 2000, at 14:26, Sterling wrote:
> Every command I put into the database dumps a whole bunch of
text and
> then the answer. For example:
>
> template1=# \l
> 001208.15:25:43.529  [2824] StartTransactionCommand
> 001208.15:25:43.529  [2824] query: SELECT
pg_database.datname as

When you start postmaster as the postgres user, redirect stdout to
a log file (or, to lose this info, use the silent option.)



--
Joel Burton, Director of Information Systems -*- jburton@scw.org
Support Center of Washington (www.scw.org)