On Fri, 2003-10-31 at 12:25, Nitz wrote:
> You were right, the volume of the data changes the optimizer's
> willingness to use indexes.
AFAICS, the optimizer seems to be making exactly the right guesses for
the production data -- i.e. there's no problem/bug.
> Another funny thing though... I ac
--- Tom Lane <[EMAIL PROTECTED]> wrote:
> ljb <[EMAIL PROTECTED]> writes:
> > [Using PostgreSQL-7.3.4 and -7.4beta5, Tcl-8.4.x.]
> > Binary data written to a Large Object with
> libpgtcl's pg_lo_write is
> > corrupted. Tcl is mangling the data - something
> to do with UTF-8
> > conversion. Examp
any windows port yet?
Hi Rod,
here is the actual production trace of the problem.
This is a table of mobile network cells and code-names devided into LAC's.
Two test cells to test with are:
test cell id #1: 900 4900035
test cell id #2: 300 5080140
You were right, the volume of the data changes the optimizer's
willingn
> TRACE:
> The original tables are much bigger, so I've tried to simplify things here.
> Please let me know if there is anything that I could help you with.
You can't do that and expect to get reasonable results. The plans will
change with the volume of data.
Send an explain analyze of the true
Hi!
SOME BACKGROUND:
I am having a rather annoying problem which I have no explonation to so
I am calling it a bug.
Currenty I am designing a rather huge database with 700+ tables and
unfortunately I am quite late to discover
this as my test data is imported via \i
the_whole_database_definition
On Thursday 30 October 2003 19:18, Bas Scheffers wrote:
> > This is not a bug. If there is not file named ~ then it can't be
> > opened.
> I am not trying to open a file named ~, I am using it as part of a file
> name, ie: ~/ewap/sql/ewap.sql. (where ~=/home/bas) This is perfectly valid
> on any
