Michael Fuhr wrote:
On Thu, Nov 17, 2005 at 10:38:50AM -0500, David Rysdam wrote:
I'm porting an application from Sybase and I've noticed that similar
application functions take 2 to 3 times longer on postgres than they
used to on the same machine running under Sybase. I've tried changing
On Thu, Nov 17, 2005 at 10:38:50AM -0500, David Rysdam wrote:
> I'm porting an application from Sybase and I've noticed that similar
> application functions take 2 to 3 times longer on postgres than they
> used to on the same machine running under Sybase. I've tried changing
> various "performa
Martijn van Oosterhout wrote:
On Thu, Nov 17, 2005 at 11:31:27AM -0500, David Rysdam wrote:
Right, it's about 100k rows and it is through libpq (pgadmin in this
case, but my app uses libpq from pgtcl). Is there a way to tell libpq
to not do what it "likes" and do what I need instead? I di
Bruno Wolff III wrote:
On Thu, Nov 17, 2005 at 11:31:27 -0500,
David Rysdam <[EMAIL PROTECTED]> wrote:
Right, it's about 100k rows and it is through libpq (pgadmin in this
case, but my app uses libpq from pgtcl). Is there a way to tell libpq
to not do what it "likes" and do what I need in
On Thu, Nov 17, 2005 at 11:31:27AM -0500, David Rysdam wrote:
> Right, it's about 100k rows and it is through libpq (pgadmin in this
> case, but my app uses libpq from pgtcl). Is there a way to tell libpq
> to not do what it "likes" and do what I need instead? I didn't see
> anything in the do
On Thu, Nov 17, 2005 at 11:31:27 -0500,
David Rysdam <[EMAIL PROTECTED]> wrote:
> Right, it's about 100k rows and it is through libpq (pgadmin in this
> case, but my app uses libpq from pgtcl). Is there a way to tell libpq
> to not do what it "likes" and do what I need instead? I didn't see
David Rysdam <[EMAIL PROTECTED]> writes:
> Right, it's about 100k rows and it is through libpq (pgadmin in this
> case, but my app uses libpq from pgtcl). Is there a way to tell libpq
> to not do what it "likes" and do what I need instead?
The only way ATM is to declare a cursor on the query an
Tom Lane wrote:
David Rysdam <[EMAIL PROTECTED]> writes:
Right now, I'm working on a test case that involves a table with ~360k
rows called "nb.sigs". My sample query is:
select * from nb.sigs where signum > 25
With no index, explain says this query costs 11341. After CREATE INDEX
on
int4, not null and the index is unique. I even tried clustering on it
to no avail.
codeWarrior wrote:
What is the data type for "signum" ???
"David Rysdam" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
I'm porting an application from Sybase and I've noticed that similar
David Rysdam <[EMAIL PROTECTED]> writes:
> Right now, I'm working on a test case that involves a table with ~360k
> rows called "nb.sigs". My sample query is:
> select * from nb.sigs where signum > 25
> With no index, explain says this query costs 11341. After CREATE INDEX
> on the signum f
What is the data type for "signum" ???
"David Rysdam" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> I'm porting an application from Sybase and I've noticed that similar
> application functions take 2 to 3 times longer on postgres than they used
> to on the same machine running
11 matches
Mail list logo