Here is an updated version of contrib/pg_stat_statements patch.
"Alex Hunsaker" wrote:
> >> I think the explain_analyze_format guc is a clever way of getting
> >> around the explain analyze verbose you proposed earlier. But I dont
> >> see any doc updates for it.
Documentation is added.
> How
Andrew Chernow wrote:
Any plans to enable the extra parameter string for notifies?
Apparently, it was seriously considered as it is a member of PGnotify
and has a reserved spot in the 'A' command sent by the backend.
Yes I plan to do it, but pressure of work has prevented me from devoting
Any plans to enable the extra parameter string for notifies? Apparently, it was
seriously considered as it is a member of PGnotify and has a reserved spot in
the 'A' command sent by the backend.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-hackers mail
Hi,
I found include/storage/itempos.h is not included from any sources.
What is it for? Should we remove it from the source tree?
struct ItemSubpositionData
typedef ItemSubpositionData *ItemSubposition;
Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
--
Sent via pgsql-
On Wed, Dec 24, 2008 at 10:08:01AM -0800, David Lee Lambert wrote:
> On Dec 17, 2:30 pm, Andrew Gierth wrote:
> > Has anyone ever managed to get uuid generation working on FreeBSD? [...]
> >
> > ([...] The only solution I could come up with was to knock
> > off a quick uuid-freebsd module that use
Jaime Casanova wrote:
On Wed, Dec 24, 2008 at 7:05 PM, KaiGai Kohei wrote:
The other need an explanation. A database superuser is allowed
to update system catalog by hand, if it is allowed by the security
policy. For example, he will be able to update "relkind" in some
of pg_class, even if it n
> Perhaps we should listen to the people that have said they don't want
> queries cancelled, even if the alternative is inconsistent answers.
I think an alternative to that would be "if the wal backlog is too
big, let current queries finish and let incoming queries wait till the
backlog gets small
On Wed, Dec 24, 2008 at 7:05 PM, KaiGai Kohei wrote:
>
> The other need an explanation. A database superuser is allowed
> to update system catalog by hand, if it is allowed by the security
> policy. For example, he will be able to update "relkind" in some
> of pg_class, even if it never happen in
On Mon, Dec 22, 2008 at 8:53 AM, Bernd Helmle wrote:
> --On Mittwoch, November 26, 2008 10:54:01 +0100 Bernd Helmle
> wrote:
>
> Okay, i've finally managed to create an updated version with (hopefully) all
> issues mentioned by Robert adressed.
>
Hi Bernd,
1) i found a crash type bug, try this:
> There is almost zero penalty for selecting incorrect MCV tuples to
> buffer in memory. Since the number of MCVs is approximately 100, the
> "overhead" is keeping these 100 tuples in memory where they *might* not
> be MCVs. The cost is the little extra memory and the checking of the
> MCVs which
2008/12/25 Pavel Stehule :
> 2008/12/25 Hitoshi Harada :
>> 2008/12/25 Greg Stark :
>>> Yeah, it seems like adding a flag like iswindowable to aggregate functions
>>> is the safest option.
>>>
>>> It would be nice if it represented an abstract property of the state
>>> function or final function ra
2008/12/25 Hitoshi Harada :
> 2008/12/25 Greg Stark :
>> Yeah, it seems like adding a flag like iswindowable to aggregate functions
>> is the safest option.
>>
>> It would be nice if it represented an abstract property of the state
>> function or final function rather than just "works with the impl
I updated the patch set of SE-PostgreSQL and related stuff (r1348)
[1/5]
http://sepgsql.googlecode.com/files/sepostgresql-sepgsql-8.4devel-3-r1348.patch
[2/5]
http://sepgsql.googlecode.com/files/sepostgresql-utils-8.4devel-3-r1348.patch
[3/5]
http://sepgsql.googlecode.com/files/sepostgresql-pol
2008/12/25 Greg Stark :
> Yeah, it seems like adding a flag like iswindowable to aggregate functions
> is the safest option.
>
> It would be nice if it represented an abstract property of the state
> function or final function rather than just "works with the implementation
> of window functions".
Yeah, it seems like adding a flag like iswindowable to aggregate
functions is the safest option.
It would be nice if it represented an abstract property of the state
function or final function rather than just "works with the
implementation of window functions". I'm not sure what that prope
15 matches
Mail list logo
