Re: 8.4.1 distinct query WITHOUT order by
От | Gary Chambers |
---|---|
Тема | Re: 8.4.1 distinct query WITHOUT order by |
Дата | |
Msg-id | 302670f20912211945n1b6684e9xb304d4508766f117@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: 8.4.1 distinct query WITHOUT order by (Scott Marlowe <scott.marlowe@gmail.com>) |
Ответы |
Re: 8.4.1 distinct query WITHOUT order by
|
Список | pgsql-sql |
> Yeah, if you're code base is that fragile, bandaging it up by jumping > through hoops in pgsql is just putting off the inevitable when it (the > code base) has to get recompiled someday anyway. I appreciate (and agree with) the concern about the fragility of the codebase. The maintainer knows that anything except adding ORDER BY is a kludge. Now, the aforementioned notwithstanding... Aside from disabling enable_hashagg (which, according to the documentation, is performance-expensive), what other options do I have? What are the ramifications of renaming the table (containing 8000 rows) and creating a view of the same name? Assuming it's possible, would the efficiency of a rule to rewrite the query be an acceptable alternative? Thanks in advance for any insight and suggestions! -- Gary Chambers /* Nothing fancy and nothing Microsoft! */
В списке pgsql-sql по дате отправления: