I wrote:
> Bruce Momjian writes:
>> Tom Lane wrote:
>>> I thought about this a bit more last night. It's certainly true that
>>> a lot of "internal" functions have comments that don't suggest that
>>> they're not meant to be used directly. What I think would be a good
>>> plan for functions that
On Wed, Mar 2, 2011 at 2:46 PM, Josh Berkus wrote:
> On 3/2/11 8:35 AM, Robert Haas wrote:
>> On Mon, Feb 7, 2011 at 1:47 PM, Josh Berkus wrote:
>>> Had to look up some stuff given the splintering of Solaris:
>>>
>>> ==
>>>
>>> Solaris 2.6 to 2.9 (Solaris 6 to Solaris 9)
>>>
>>>
On 3/2/11 8:35 AM, Robert Haas wrote:
> On Mon, Feb 7, 2011 at 1:47 PM, Josh Berkus wrote:
>> Had to look up some stuff given the splintering of Solaris:
>>
>> ==
>>
>> Solaris 2.6 to 2.9 (Solaris 6 to Solaris 9)
>>
>>The default maximum size of a shared memory segment is too l
On Mon, Feb 7, 2011 at 1:47 PM, Josh Berkus wrote:
> Had to look up some stuff given the splintering of Solaris:
>
> ==
>
> Solaris 2.6 to 2.9 (Solaris 6 to Solaris 9)
>
> The default maximum size of a shared memory segment is too low for
> PostgreSQL. The relevant settings can
Marko Tiikkaja writes:
> The recent commit 09b49a8439fde63826f93f55430868cf2585644b claims:
> +Time spent firing triggers, if any, is charged to the Insert,
> +Update, or Delete node, and is also shown separately for each trigger.
> +Note, however, that deferred triggers will not be f
Hi,
The recent commit 09b49a8439fde63826f93f55430868cf2585644b claims:
+Time spent firing triggers, if any, is charged to the Insert,
+Update, or Delete node, and is also shown separately for each trigger.
+Note, however, that deferred triggers will not be fired until end of
+tra
