On Thu, Jan 10, 2008 at 11:08:16AM -0500, Andrew Sullivan wrote:
> I mean this sincerely and not snidely: get another job. 7.3.20 was the last
Err, 7.3.21, I meant, of course. Sorry.
A
---(end of broadcast)---
TIP 4: Have you searched our list a
On Wed, Jan 09, 2008 at 06:19:40PM -0500, Brown, Richard wrote:
>
> - We are using PostgreSQL 7.3.4, and am locked into this version. I would
> upgrade if I could, but the decision is not mine.
I mean this sincerely and not snidely: get another job. 7.3.20 was the last
release in the 7.3 series.
Hi All,
First, some background:
- We are using PostgreSQL 7.3.4, and am locked into this version. I would
upgrade if I could, but the decision is not mine.
- The table referred to below is 120+ million rows, and has a width of 27
columns (15 smallints, 5 integers, 4 dates, 1 integer[], 1 single c
On Wednesday 09 January 2008 20:09, Greg Smith wrote:
> On Wed, 9 Jan 2008, Richard Brown wrote:
> > - We are using PostgreSQL 7.3.4, and am locked into this version. I would
> > upgrade if I could, but the decision is not mine.
>
> Just make sure you CYA so when said server eats itself the decisio
On Wed, 9 Jan 2008, Richard Brown wrote:
- We are using PostgreSQL 7.3.4, and am locked into this version. I would
upgrade if I could, but the decision is not mine.
Just make sure you CYA so when said server eats itself the decision maker
can't point the finger at you. Give them a copy of a
"Richard Brown" <[EMAIL PROTECTED]> writes:
> - We are using PostgreSQL 7.3.4, and am locked into this version. I would
> upgrade if I could, but the decision is not mine.
They won't even let you update to 7.3.something-reasonably-current ?
Resign. Go find a job with a boss whose IQ is above roo
Hi All,
First, some background:
- We are using PostgreSQL 7.3.4, and am locked into this version. I would
upgrade if I could, but the decision is not mine.
- The table referred to below is 120+ million rows, and has a width of 27
columns (15 smallints, 5 integers, 4 dates, 1 integer[], 1 single c
