"kopra" <[EMAIL PROTECTED]> writes:
>> If nothing, how about
>> select oid from pg_class where relname = 'hasil_lab';
> I find different number...
> any clue ?
If you want to be walked through this, you're going to have to offer
more than minimal amounts of information --- like, for example, the
Ray Ontko <[EMAIL PROTECTED]> writes:
> BTW, Are you sure that you need to do the "distinct"?
That's a good question to ask.
> If you do,
> then you might try putting the order_date column first in the
> select list. The distinct is requiring that all the rows be sorted
> so that they can be un
Please use "explain analyze" instead of just "explain"; the additional
information is very helpful to see where the query is actually spending
time.
Have you considered clustering on the order_date index? We have
seen dramatic improvements in situations where the table is
physically ordered by t
>> pg_dumpall seems to do this for me, without any command-line args
>> needed. Am I correct in saying that 'pg_dumpall > filename' will
>> produce
>> a PostgreSQL dump that includes _everything_ I need to go from a clean
>> PG install to accepting connections again with data intact? Users,
>>
>
> Hmm ... is that the same relation? What do you get from
> select * from pg_class where oid = 748580;
I not find that number
> If nothing, how about
> select oid from pg_class where relname = 'hasil_lab';
>
I find different number...
any clue ?
Regards
Eko Pranoto
--
