On Wed, Jul 06, 2005 at 02:32:31PM -0400, Bruce Momjian wrote:
>
> This message is from the backend exiting abruptly. Is isn't an "ERROR"
> as we define it for logging purposes. That's why there is nothing in
> the logs. I recommend turning on log_statement which prints before the
> query is run.
I hadn't thought of the error that way. I do have query logging on,
and if I run that query directly, it finds the data I'd expect. It's
a small table, or really three of them, all small for the time being.
select it.id, it.it_class_id, it.it_code_version_id,
it.it_data_version, it.note, it_class.class, it_class.id,
it_code_version.version, it_code_version.id, it_class.id,
it_code_version.id from it join it_class on (it_class.id =
it.it_class_id) join it_code_version on (it_code_version.id =
it.it_code_version_id) where class = ? AND version = ? AND
it_data_version > ?
--
... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
Felix Finch: scarecrow repairman & rocket surgeon / felix@xxxxxxxxxxx
GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
