Gurjeet Singh writes:
> On Wed, Apr 10, 2013 at 11:10 PM, Tom Lane wrote:
>> The point you're missing is that the synchronization is self-enforcing:
> Let's consider a pathological case where a scan is performed by a user
> controlled cursor, whose scan speed depends on how fast the user presses
On Wed, Apr 10, 2013 at 11:10 PM, Tom Lane wrote:
> Gurjeet Singh writes:
> > If I'm reading the code right [1], this GUC does not actually
> *synchronize*
> > the scans, but instead just makes sure that a new scan starts from a
> block
> > that was reported by some other backend performing a sc
Gurjeet Singh writes:
> If I'm reading the code right [1], this GUC does not actually *synchronize*
> the scans, but instead just makes sure that a new scan starts from a block
> that was reported by some other backend performing a scan on the same
> relation.
Well, that's the only *direct* effec
If I'm reading the code right [1], this GUC does not actually *synchronize*
the scans, but instead just makes sure that a new scan starts from a block
that was reported by some other backend performing a scan on the same
relation.
Since the backends scanning the relation may be processing the rela
Hi list,
I was checking out the new JSON features coming in 9.3, really cool stuff!
I noticed a small discrepancy in the documentation, the
"hstore_to_json_loose" example uses hstore_to_json() by accident.
Patch attached.
Regards,
Marti
0001-Fix-discrepancy-in-hstore_to_json_loose-documentati
On Wed, Apr 10, 2013 at 5:48 AM, Scott Marlowe wrote:
>
> On Tue, Apr 9, 2013 at 9:30 PM, Peter Eisentraut wrote:
>>
>> Since OpenSolaris was yanked from the net, the DTrace link in our
>> documentation points to approximately nowhere. I propose the attached
>> patch with a link to Wikipedia ins
