On Thu, Apr 20, 2006 at 11:56:32AM -0400, Tom Lane wrote:
Martijn van Oosterhout kleptog@svana.org writes:
About the only thing in the backend I found interesting was this:
src/backend/utils/hash/dynahash.c function hash_create
I wonder if we shouldn't just remove the hash_destroy calls in
Is there any way to control (enable/disable) some parts of BKI file?
(actually, I mean not BKI files themselves but their prototypes -
include/catalog/pg_*.h)
For example, I add some function to include/catalog/pg_proc.h and want
to have ability to enable/disable it during installation process
On Mon, Aug 14, 2006 at 12:31:30PM +0400, Nikolay Samokhvalov wrote:
Is there any way to control (enable/disable) some parts of BKI file?
(actually, I mean not BKI files themselves but their prototypes -
include/catalog/pg_*.h)
No, because that's a bad idea. Even time somethin gthe catalog
Hi Tom,
It now works like a charm!
Many thanks.
Best regards,
On Sun, 13 Aug 2006, Tom Lane wrote:
Date: Sun, 13 Aug 2006 14:00:37 -0400
From: Tom Lane [EMAIL PROTECTED]
To: ohp@pyrenet.fr
Cc: pgsql-hackers list pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Warthog failing
Martijn van Oosterhout kleptog@svana.org writes:
On Thu, Apr 20, 2006 at 11:56:32AM -0400, Tom Lane wrote:
I wonder if we shouldn't just remove the hash_destroy calls in
hash_create's failure paths. hash_destroy is explicitly not gonna
work on a shared-memory hashtable, and in all other cases
Martijn van Oosterhout kleptog@svana.org writes:
On Mon, Aug 14, 2006 at 12:31:30PM +0400, Nikolay Samokhvalov wrote:
Is there any way to control (enable/disable) some parts of BKI file?
Sounds like you really want your function to be an external module. In
that case you can simply ship an
On Mon, Aug 14, 2006 at 08:09:36AM -0400, Tom Lane wrote:
Any thoughts on this? Make it a TODO item, document it, or simply
ignore it?
It's like a two-line patch, so hardly worth putting in TODO ... might
as well just do it. IIRC the motivation is mostly to silence a
Coverity warning?
Martijn van Oosterhout kleptog@svana.org writes:
On Mon, Aug 14, 2006 at 08:09:36AM -0400, Tom Lane wrote:
It's like a two-line patch, so hardly worth putting in TODO ... might
as well just do it. IIRC the motivation is mostly to silence a
Coverity warning?
Well sort of. I can also just
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Jim C. Nasby) wrote:
On Wed, Aug 09, 2006 at 08:31:42AM -0400, Perez wrote:
Every once in a while people talk about collecting better statistics,
correlating multi-column correlations etc. But there never seems to be
a way to collect
On Sun, Aug 13, 2006 at 03:54:18PM -0400, Tom Lane wrote:
which is that you can use aggregate functions in the RETURNING list and
get a single-row result that is aggregated across all affected rows.
It's too late to consider implementing that for 8.2, I fear, but I think
maybe we should put it
Based on how small this patch is and the demonstrated desire for this
behavior, can we consider putting this in 8.2, even though we're past
the deadline?
On Sun, Aug 13, 2006 at 10:03:30PM -0500, Jaime Casanova wrote:
On 8/13/06, Tom Lane [EMAIL PROTECTED] wrote:
Jaime Casanova [EMAIL
On Sun, Aug 13, 2006 at 07:01:13PM -0400, Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Tom Lane wrote:
This reminds me that even though the V3-protocol code has been in there
since 7.4, we don't have nearly complete test coverage on it. It'd be a
good idea to have some basic
Bruce Momjian wrote:
FYI, I will be at LinuxWorld San Francisco tomorrow(Monday) through
Friday. I will have only occasional Internet connectivity, so there
might be delays in my handling open issues.
Hopefully your Internet issues won't be as bad as mine. I have to sit in
the hall at the
OK, point taken. I'll admit that I had hopes for it for PR reasons, which
is not usually why we make decisions. It would be cool to be the first
database system to ship with any implementation of Full Disjunctions, and
I can't announce that if it's on pgFoundry.
You could announce it
Andrew Dunstan wrote:
It has just been pointed out to me that the list archives seem to have
stopped being updated last Wednesday. Any idea why?
That is really more of a question for -www and (possibly) cmd. Looking
into this now.
I am showing archives as of the 08/14?
Joshua D. Drake
Marc G. Fournier wrote:
Fixed ... the 'auto run' was commented out when I was rebuilding it
all for the pre-July / post-July changes (old vs new) and failed to
uncomment the cron job after ...
Ahhh woops... cool.
should be updated within the next hour or so ...
On Sat, 12 Aug 2006,
Perez wrote:
I thought, from watching the list for a while, that the planner
statistics needed were known but that how to gather the statistics
was not?
I think over the course of the discussion we have figured out that we
would like to have cross-column correlation statistics. The precise
On Sun, 2006-08-13 at 22:50 -0400, Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
This issue is closed, right?
We've agreed we need two functions, but it's not done yet. Seems pretty
trivial though ...
Just back from India. I'll work on this tonight.
--
Simon Riggs
Ühel kenal päeval, E, 2006-08-14 kell 18:21, kirjutas Peter Eisentraut:
Perez wrote:
I thought, from watching the list for a while, that the planner
statistics needed were known but that how to gather the statistics
was not?
I think over the course of the discussion we have figured out
Andrew Dunstan [EMAIL PROTECTED] writes:
I am more than somewhat perplexed as to why the NUL device should be a
security risk ... what are they thinking??
Frankly, I don't believe it; even Microsoft can't be that stupid.
And I can't find any suggestion that they've done this in a google
search.
*
domains.c contains the followng snippet in domain_in():
else* *if* (my_extra-domain_type != domainType)
domain_state_setup(my_extra, domainType, false,
fcinfo-flinfo-fn_mcxt);
We were just looking at this code (in the
Andrew Dunstan [EMAIL PROTECTED] writes:
domains.c contains the followng snippet in domain_in():
else* *if* (my_extra-domain_type != domainType)
domain_state_setup(my_extra, domainType, false,
fcinfo-flinfo-fn_mcxt);
We were
Jim C. Nasby [EMAIL PROTECTED] writes:
Aggregates sound interesting, though I'm not sure how useful they'd
actually be. I think something like
FOR v_row IN (UPDATE ... RETURNING ...)
would be a lot more useful (if it's not already in the patch).
It's not. I thought about it for a bit
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
domains.c contains the followng snippet in domain_in():
else* if (my_extra-domain_type != domainType)
domain_state_setup(my_extra, domainType, false,
Gavin Sherry [EMAIL PROTECTED] writes:
Attached is an update to the patch implementing bitmap indexes Jie sent
last week.
What's the current status of this patch ... has any work been done since
the first of the month?
I suppose the patch as given here no longer applies to HEAD, because of
On Mon, 14 Aug 2006, Tom Lane wrote:
Gavin Sherry [EMAIL PROTECTED] writes:
Attached is an update to the patch implementing bitmap indexes Jie sent
last week.
What's the current status of this patch ... has any work been done since
the first of the month?
Yes. I am tidying up the
Gavin Sherry [EMAIL PROTECTED] writes:
I will post an updated patch in a few days time.
OK. Do you want me to work on the discussed amgetmulti change, or would
that just be joggling your elbow at the moment?
regards, tom lane
---(end of
On Mon, 14 Aug 2006, Tom Lane wrote:
Gavin Sherry [EMAIL PROTECTED] writes:
I will post an updated patch in a few days time.
OK. Do you want me to work on the discussed amgetmulti change, or would
that just be joggling your elbow at the moment?
Yes, that would be joggling ;).
The
Gavin Sherry [EMAIL PROTECTED] writes:
One of the main reasons for the uglification of the executor in Jie's
original patch was that she wanted to avoid the inefficiency of
translating the on disk bitmap representation to the TID bitmap
representation.
Offhand that seems like
On Mon, 14 Aug 2006, Tom Lane wrote:
Gavin Sherry [EMAIL PROTECTED] writes:
One of the main reasons for the uglification of the executor in Jie's
original patch was that she wanted to avoid the inefficiency of
translating the on disk bitmap representation to the TID bitmap
Dear Community members,
It is with great enthuasim I announce that I have accepted an offer from
Joshua D. Drake of Command Prompt Inc, to join his team. As former Vice
President of Software Development with Wavefire Technologies Corp, I endeavor
to leverage over 10 years of technical
Wouldn't it be weird if an update to pg_stat_activity.current_query
actually ran that query for the selected backend:
UPDATE pg_stat_activity SET current_query = SELECT 1
WHERE procpid = 19522;
--
Bruce Momjian [EMAIL PROTECTED]
EnterpriseDBhttp://www.enterprisedb.com
32 matches
Mail list logo
