Simon Riggs wrote:
> OK, thats what I hoped you'd say. With a prepared query all of the
> statements execute the same plan, so you don't need to know the exact
> parameters.
This isn't true in 8.0 if you are using the unnamed statement (as the
JDBC driver does in some cases): the plan chosen depe
On Fri, 2005-04-08 at 00:51 +0200, Palle Girgensohn wrote:
> --On torsdag, april 07, 2005 23.31.52 +0100 Simon Riggs
> <[EMAIL PROTECTED]> wrote:
>
> > On Wed, 2005-04-06 at 15:01 +0200, Palle Girgensohn wrote:
> >> I really need to know the *real* arguments...
> >
> > Why do you need to log the
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
>> SIGQUIT is supposed to do that.
> Seems to be a libreadline thing:
No, it's a built-in thing. See "man stty", "man tty(4)", "man termio"
or related topics depending on your platform. The point is that the
kernel terminal driver takes that a
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> tar sizes look right compared to 8.0.1 ... please check her over to make
> sure there are no problems ...
Looks good from here.
regards, tom lane
---(end of broadcast)---
TIP
1. Fire up psql.
2. Press Ctrl-4
3. Crash, core dump...
SIGQUIT is supposed to do that.
Seems to be a libreadline thing:
#0 0x2827fd60 in sigprocmask () from /usr/lib/libc.so.4
#1 0x281f5adb in _rl_savestring () from /usr/lib/libreadline.so.4
#2 0xbfbfffac in ?? ()
#3 0x281f2254 in rl_read_key
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> 1. Fire up psql.
> 2. Press Ctrl-4
> 3. Crash, core dump...
SIGQUIT is supposed to do that.
regards, tom lane
---(end of broadcast)---
TIP 3: if posting/reading through U
Hi,
1. Fire up psql.
2. Press Ctrl-4
3. Crash, core dump...
Chris
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Will be on the main ftp site within the next 30 minutes ...
tar sizes look right compared to 8.0.1 ... please check her over to make
sure there are no problems ...
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: [EMAIL PROTECTED] Yahoo!: yscrappy
Neil Conway wrote:
I'd like to make add_missing_from=false the default for 8.1. Any
objections?
FYI, I've applied a patch that makes this change to CVS HEAD.
-Neil
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTEC
On Fri, Apr 08, 2005 at 02:27:46AM +0200, Bernd Helmle wrote:
> --On Dienstag, April 05, 2005 16:19:54 -0400 Tom Lane <[EMAIL PROTECTED]>
> wrote:
>
> >I've gotten a bee in my bonnet again about Resdom being wasteful.
> >There is no case where Resdom appears without TargetEntry, nor vice
> >versa
--On Dienstag, April 05, 2005 16:19:54 -0400 Tom Lane <[EMAIL PROTECTED]>
wrote:
I've gotten a bee in my bonnet again about Resdom being wasteful.
There is no case where Resdom appears without TargetEntry, nor vice
versa, so we ought to fold them into a single node type. Is anyone
out there work
--On torsdag, april 07, 2005 23.31.52 +0100 Simon Riggs
<[EMAIL PROTECTED]> wrote:
On Wed, 2005-04-06 at 15:01 +0200, Palle Girgensohn wrote:
I really need to know the *real* arguments...
Why do you need to log the arguments as well?
Debugging purposes. If I fealize there are queries hogging the
On Wed, 2005-04-06 at 15:01 +0200, Palle Girgensohn wrote:
> I really need to know the *real* arguments...
Why do you need to log the arguments as well?
Thanks,
Best Regards, Simon Riggs
---(end of broadcast)---
TIP 3: if posting/reading through
On Wed, Apr 06, 2005 at 06:35:10PM -0400, Tom Lane wrote:
> "Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> > On Wed, Apr 06, 2005 at 06:09:37PM -0400, Tom Lane wrote:
> >> Can anyone suggest a more general rule? Do we need for example to
> >> consider whether the relation membership is the same in t
Bruno Wolff III <[EMAIL PROTECTED]> writes:
> Tom Lane <[EMAIL PROTECTED]> wrote:
>> Can anyone suggest a more general rule?
> I think it makes sense to guess that a smaller fraction of the rows will
> be returned when a column value is bounded above and below than if it
> is only bounded on one
Karel Zak <[EMAIL PROTECTED]> writes:
> Why is there so different "Total runtime" for ('now'::text)::date) and
> '2005-04-06'::date ?
> I think both is constant during execution.
Not at all. text_date() is not immutable so it has to be applied during
execution. The other one is just a constant.
Alexey Slynko <[EMAIL PROTECTED]> writes:
> I have found comments in backend/catalog/index.c, that
> index_build closes the passed rels ( heapRelation and indexRelation ).
Bootstrap mode does it differently. I've never really felt motivated to
understand why in any detail. Presumably it was once
On Wed, Apr 06, 2005 at 18:09:37 -0400,
Tom Lane <[EMAIL PROTECTED]> wrote:
>
> Can anyone suggest a more general rule? Do we need for example to
> consider whether the relation membership is the same in two clauses
> that might be opposite sides of a range restriction? It seems like
>
>
On Thu, Apr 07, 2005 at 02:34:03PM +0800, Qingqing Zhou wrote:
>
> "Alvaro Herrera" <[EMAIL PROTECTED]> writes
> > Because we can't reuse MultiXactIds at system crash (else we risk taking
> > an Id which is already stored in some tuple), we need to XLog it. Not
> > at the locking operation, becau
Why is there so different "Total runtime" for ('now'::text)::date) and
'2005-04-06'::date ?
I think both is constant during execution.
CREATE TABLE test (
_time timestamp with time zone,
_platform character(5),
_tld character(5)
) WITHOUT OIDS;
explain analyze SELECT count(
--On torsdag, april 07, 2005 14.34.22 +1200 Oliver Jowett
<[EMAIL PROTECTED]> wrote:
Greg Stark wrote:
Palle Girgensohn <[EMAIL PROTECTED]> writes:
When setting log_statement = all, and using JDBC PreparedStatements, I
get $n in the log where the real arguments used to be in previous
versions of
Hi,
I have found comments in backend/catalog/index.c, that
index_build closes the passed rels ( heapRelation and indexRelation ).
But in backend/access/nbtree/nbtree.c I see something like this:
if (IsNormalProcessingMode())
{
heap_close(heap, NoLock);
22 matches
Mail list logo
