Tom Lane wrote:
Ferruccio Zamuner <[EMAIL PROTECTED]> writes:
I need to have in the log_line_prefix the search_path where the query
has run.
So last week I've started to read elog.c and I was thinking about a
small patch there using a new "%S" option.
There
Hi,
I need to have in the log_line_prefix the search_path where the query
has run.
So last week I've started to read elog.c and I was thinking about a
small patch there using a new "%S" option.
First I've introduced a small code:
case 'S':
{
List *search_path = fetch_se
Richard Huxton said:
> Ferruccio Zamuner wrote:
>> Hi,
>>
>> I've following select, and I expect to receive a single record as result
>> from it:
>>
>> select c.id
>> from copie as c
>> where c.enum=46857 and
>> c.condizio_p
Hi,
I've following select, and I expect to receive a single record as result from it:
select c.id
from copie as c
where c.enum=46857 and
c.condizio_prestito = 'A' and
c.id not in (select id_copia from testi_fermi_prenotati) and
c.id not in (select id_copia from prestiti);
Hi,
someone asks me about an utility to check any PostgreSQL database
data to be sure that:
1) there is not any page corrupted
(by a memory fault or a damaged disk)
2) re-check any constraint inserted into the database
I really don't know if PostgreSQL itself has any crc check on
its pages.
From: Horst Herb <[EMAIL PROTECTED]>
Date: Mon, 1 Jan 2001 10:09:52 +1100
>> create table a (
>>id serial primary key,
>>something text
>> );
>>
>> create table b (
>>morething text
>> ) inherits (a);
>>
>> create table c (
>>trouble int references b;
>> );
Hi,
some months ago I've asked for a suggestion for this bug:
create table a (
id serial primary key,
something text
);
create table b (
morething text
) inherits (a);
create table c (
trouble int references b;
);
NOTICE: CREATE TABLE will create implicit trigger(s
