>Marc Mamin-2 wrote
>> I would misuse GUC variables for this.
>> (using the functions current_setting and set_config)
>>
>> define a set get and switch fuction (I use operators for better
>> readability)
>> something like:
>>
>> select 'a' ==> 'foo'
>> 'a'
>> select 'b' <==> 'foo'
>> 'a'
>> select
Alan Nilsson writes:
> I ran into something tonight that seems relevant here, or certainly related:
> I recently updated my app(s) libpq version from 9.1 to 9.3 and immediately I
> starting seeing:
> row number 0 is out of range 0..-1
> spewed to stdout.
> I traced it down to this code:
>
On 25.10.2013 19:04, Scott Marlowe wrote:
> On Fri, Oct 25, 2013 at 8:29 AM, Rahila Syed wrote:
>>
>> Configurations of my machine is:
>>
>> Processors: Xeon E5-2650 Processor Kit
>> Intel® Xeon ® Processor E5-2650 (2 GHz, 8C/16T,
>> 20 MB) * 2 nos
>>
>>
>> RAM : 32GB DDR3
Hi,
On 24.10.2013 23:18, Alban Hertroys wrote:
> On Oct 24, 2013, at 18:10, maillis...@gmail.com wrote:
>
>> Thank you for the answers. I'm still confused. If fsync is not
>> replicated to the slave, then how is replication affected by a
>> corrupt master? If the master dies and there's a commit
oops sorry to be unclear, the code below is my code in my app.
What I am saying is that something changed in 90300 that causes libpq to spew
to stdout where it had not in libpq 90102 & 90203.
I guess i am blaming the messenger because there should be no messenger.
Regardless of how badly I m
