Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom, do you want this fixed for 8.2.X?
>
> > Tom Lane wrote:
> >> Yeah. I'd say that intarray's attempt to override the default status of
> >> the built-in gin opclass is simply a bad idea and should be removed.
>
> I don't recall h
Am Montag, 2. April 2007 16:48 schrieb Denis Lishtovny:
> I want to output result of query with double newline record separated.
>
> For example:
>
> psql -At -P recordsep="\n\n" -U postgres -c "select generate_series(1,3)"
"\n" is not a newline, it's a "\" followed by an "n". You need to actuall
Denis Lishtovny wrote:
> Hello All.
>
>
>
> I want to output result of query with double newline record separated.
>
> For example:
>
> psql -At -P recordsep="\n\n" -U postgres -c "select generate_series(1,3)"
What this says is that there's no interpolation of escapes in recordsep.
Try putt
Hello All.
I want to output result of query with double newline record separated.
For example:
psql -At -P recordsep="\n\n" -U postgres -c "select generate_series(1,3)"
1
2
3
But my result is:
psql -At -P recordsep="\n\n" -U postgres -d chronopay -c "select
generate_series(1,3)"
1
Martin Pitt wrote:
> Hi Tom, hi Mark,
>
> Tom, thank you for having a look into this!
>
> Tom Lane [2007-03-29 13:49 -0400]:
>
>> Martin Pitt <[EMAIL PROTECTED]> writes:
>>
>>> https://launchpad.net/bugs/93042 has symbolic gdb backtraces of all
>>> three processes that are involved.
>>>
It seems that solution with a shared lock on t1 is working.
Though in this case I have the following questions:
1. If the session in which v1 was created is terminated abnormally, then
there is a chance of the initial situation iteration, because v1 is a
temporary view. What about this?
2. If I
