are the reasons for the difference? And when does one approach is more
preferable than another?
Regards,
Bramandia R.
On Sat, Dec 13, 2008 at 10:36 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Bramandia Ramadhana braman...@gmail.com writes:
Hmm how if an upper level node needs to store (for future use
I see. Thanks for the advice. I would research on how to use tuplestore
object.
Regards,
Bramandia R.
On Sat, Dec 13, 2008 at 10:36 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Bramandia Ramadhana braman...@gmail.com writes:
Hmm how if an upper level node needs to store (for future use
?
Regards,
Bramandia R.
On Fri, Dec 12, 2008 at 9:13 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Bramandia Ramadhana braman...@gmail.com writes:
As per title, what is the lifetime of the virtual tuple TupleTableSlot*
returned by ExecProcNode?
Until you next call that same plan node
Hello,
As per title, what is the lifetime of the virtual tuple TupleTableSlot*
returned by ExecProcNode?
Any help would be appreciated.
Regards,
Bramandia R.
Yes, I use --enable-debug as an option in configure
Regards,
Bramandia R.
On Mon, Nov 17, 2008 at 2:11 PM, Tom Lane [EMAIL PROTECTED] wrote:
Bramandia Ramadhana [EMAIL PROTECTED] writes:
Hm the backtrace() method does not give the line numbers of the methods
in
the stack trace, it only
[EMAIL PROTECTED]wrote:
Bramandia Ramadhana wrote:
Is there any way to print out the stack trace of the current location?
Not sure if Postgres has something in the utils for that.
You can use backtrace() in glibc. Solaris 9 libc has printstack(). Not sure
what's available for Windows.
I am
Hi all,
Is there any way to print out the stack trace of the current location?
I am looking for something like print_stack_trace(); that I can insert in
arbitrary location in the code.
Thank you,
Regards,
Bramandia R.
Dear All,
I took a look at the source code for hash join this morning and I realized
that the block nested loop join is somewhat similar to that.
Thanks for the discussions.
Bramandia R.
On Fri, Oct 10, 2008 at 8:19 PM, Tom Lane [EMAIL PROTECTED] wrote:
Gregory Stark [EMAIL PROTECTED]
Thanks for the clarifications.
Just for curiosity, is there any reason of not having block nested-loop join
implementation? Is it rarely useful?
As far as I am aware of, in the case of cross product of two tables, block
nested-loop join is the most efficient algorithm.
Regards,
Bramandia R.
Hi all,
I am new to postgresql. I am currently doing research to optimize the query
performance of RDBMS, specifically postgresql. Hence, I am currently reading
out the code to understand the implementation of various query evaluation
algorithm in postgresql.
Currently, I am investigating the
10 matches
Mail list logo
