| From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
|---|---|
| To: | Roman <zotov(at)oe-it(dot)ru> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #5542: Query optimization problem |
| Date: | 2010-07-07 01:34:51 |
| Message-ID: | 4C33D9BB.1010603@postnewspapers.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 06/07/10 14:43, Roman wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5542
> Logged by: Roman
> Email address: zotov(at)oe-it(dot)ru
> PostgreSQL version: 9.0
> Operating system: Win7 x64
> Description: Query optimization problem
> Details:
On the bug report form, you will have seen a note telling you that this
form is only for bug reports. If you want help with optimization,
contact the pgsql-performance mailing list.
Are you actually reporting an issue with PostgreSQL's behavior that's
unclear from your post? Or are you just asking for help with a query?
--
Craig Ringer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gurjeet Singh | 2010-07-07 04:07:38 | Negative result with (now()-previously_inserted_timestamp) |
| Previous Message | Lou Picciano | 2010-07-06 23:37:46 | Location of certs -Windows 7 SSL mode? |