Обсуждение: Debug information

Hallo,

I'm working on porting Oracle schema to PostgreSQL. Now I habe the whole
schema in PostgreSQL. But there are some problems in our application in
some sql queries. I get following errors.

ERROR:  Unable to identify an operator '<=' for types 'numeric' and 'double
precision'
         You will have to retype this query using an explicit cast

Its possible to display the queries in debug print out ftom PostgreSQL with
queries which failed? If yep, how?


Best Regards,
Rafal

You can display a lot of debug info setting up loggin.  Make the following
changes in your postgresql.conf file for some basic logging.  The higher up
you go with the debug level, the more info you'll get.

     debug_level = 2 # range 0-16
     debug_print_query = true
     debug_pretty_print = true

regards,

Devinder Rajput
Stores Division Corporate Offices
Chicago, IL
(773) 442-6474



   
                    "Rafal Kedziorski"
   
                    <rafcio@polonium.de>         To:     pgsql-admin@postgresql.org
   
                    Sent by:                     cc:
   
                    pgsql-admin-owner@post       Subject:     [ADMIN] Debug information
   
                    gresql.org
   

   

   
                    10/07/2002 06:01 PM
   

   

   




Hallo,

I'm working on porting Oracle schema to PostgreSQL. Now I habe the whole
schema in PostgreSQL. But there are some problems in our application in
some sql queries. I get following errors.

ERROR:  Unable to identify an operator '<=' for types 'numeric' and 'double
precision'
         You will have to retype this query using an explicit cast

Its possible to display the queries in debug print out ftom PostgreSQL with
queries which failed? If yep, how?


Best Regards,
Rafal


---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org

Hallo,

I found in reference.pdf small part about debug level. Where can I read
more about the 17 debug levels?


Best Regards,
Rafal

At 18:06 07.10.2002 -0500, Devinder K Rajput wrote:

>You can display a lot of debug info setting up loggin.  Make the following
>changes in your postgresql.conf file for some basic logging.  The higher up
>you go with the debug level, the more info you'll get.
>
>      debug_level = 2 # range 0-16
>      debug_print_query = true
>      debug_pretty_print = true
>
>regards,
>
>Devinder Rajput
>Stores Division Corporate Offices
>Chicago, IL
>(773) 442-6474
>
>
>
>
>                     "Rafal
> Kedziorski"
>
>                     <rafcio@polonium.de>         To:
> pgsql-admin@postgresql.org
>                     Sent
> by:                     cc:
>
>                     pgsql-admin-owner@post       Subject:     [ADMIN]
> Debug information
>                     gresql.org
>
>
>
>
>
>                     10/07/2002 06:01
> PM
>
>
>
>
>
>
>
>
>
>Hallo,
>
>I'm working on porting Oracle schema to PostgreSQL. Now I habe the whole
>schema in PostgreSQL. But there are some problems in our application in
>some sql queries. I get following errors.
>
>ERROR:  Unable to identify an operator '<=' for types 'numeric' and 'double
>precision'
>          You will have to retype this query using an explicit cast
>
>Its possible to display the queries in debug print out ftom PostgreSQL with
>queries which failed? If yep, how?
>
>
>Best Regards,
>Rafal
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org

POLONIUM-Team wrote:
> Hallo,
>
> I found in reference.pdf small part about debug level. Where can I read
> more about the 17 debug levels?

The levels are really only 1-5, and they just represent increasing
amounts of detail.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073