Skip site navigation (1) Skip section navigation (2)

Re: Exec statement logging

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Exec statement logging
Date: 2005-05-16 19:41:39
Message-ID: 20651.1116272499@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-patches
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> a null for the prepare string.  Also, rather than change the API for
> pg_parse_query(), I use a global variable that I check after the
> function call.

This is horribly ugly and will doubtless lead to pfree crashes.  What
was the point again?

			regards, tom lane

In response to

Responses

pgsql-patches by date

Next:From: Bruce MomjianDate: 2005-05-16 22:40:40
Subject: Re: Exec statement logging
Previous:From: Bruce MomjianDate: 2005-05-16 19:24:27
Subject: Re: Exec statement logging

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group