| From: | "Lee McKeeman" <lmckeeman(at)opushealthcare(dot)com> |
|---|---|
| To: | <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Status of issue 4593 |
| Date: | 2009-01-05 03:09:28 |
| Message-ID: | CB20429AE660CB43A946BF9D61C9A2B60D585C@ohsmail.opushealthcare.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
This may not be the appropriate place to check this, but when I filed
the bug with the tracking number 4593, in relation to some sort order
behavior which seemed erroneous to me. I didn't know how I would be
notified if this was actually considered a bug, etc. so I thought I'd
post here and see what I came up with. If there is a more appropriate
means of tracking bugs by number, please let me know.
Thank you,
Lee McKeeman
| From | Date | Subject | |
|---|---|---|---|
| Next Message | V KUMAR | 2009-01-05 07:25:56 | BUG #4601: Data saving and opening problem |
| Previous Message | Tom Lane | 2009-01-04 23:00:29 | Re: Debian Bug#506196: postgresql: consume too much power when idle (>10 wakeups/second) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2009-01-05 06:06:57 | Re: contrib/pg_stat_statements 1226 |
| Previous Message | Tom Lane | 2009-01-05 03:05:35 | Re: Many "loaded library" logs by preload libraries |