* Brickley Jeff-RA9607 <[EMAIL PROTECTED]> [31.03.2003 19:35]:
> Okay..I'm going to start ranting now!
> Please remove my name from this list!!! I've unsubscribed 10 ways til Tuesday
> I realize I'm broadcasting this but hopefully something will change. Does anyone
> have the personal email ad
check :
http://developer.postgresql.org/docs/postgres/release-7-3.html
for advantages of 7.3 over 7.2.x.
this only gives overview , read HISTORY file for more details.
> hi everybody,
>
> i checked through documentation but couldn't find the
> list of bugs that got fixed in 7.3 release as wel
On Mon, 2003-03-31 at 07:54, DHS Webmaster wrote:
> Just a quickie. We are planning an upgrade from 7.1.3 to 7.3. Since we
> have to bring down our production server to do it we are planning on
> killing all the birds with one shot. We are running RH 7.1 and were
> planning on using RH 8. After rea
hi everybody,
i checked through documentation but couldn't find the
list of bugs that got fixed in 7.3 release as well as
new feature set introduced in 7.3 or any performance
improvements etc...when compared to 7.2
Reason for asking this is that, i'd like to make a
point to my management for usin
Hello,
Just a quickie. We are planning an upgrade from 7.1.3 to 7.3. Since we
have to bring down our production server to do it we are planning on
killing all the birds with one shot. We are running RH 7.1 and were
planning on using RH 8. After reading a little bit recently here and
there and insta
Justin Clift wrote:
> Josh Berkus wrote:
> >Guys,
> >
> >>This is what techdocs.postgresql.org is for.
> >
> >I've been thinking for some time that we need a Postgresql resouce site
> >that's more open to multiple contributors than the current hard-coded HTML
> >of Techdocs. I was planning on e
> Are you sure your restoring to an empty database? If you try to restore
> your dump into the database you dumped it from (without first
> drop/create) it will take forever as you'll have all kinds of data
> collisions (imagine every insert into a table erroring out due to
> duplicate primary key)
