| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alex Pilosov <alex(at)pilosoft(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: sanity of using -current? |
| Date: | 2000-10-26 15:05:01 |
| Message-ID: | 5676.972572701@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alex Pilosov <alex(at)pilosoft(dot)com> writes:
> I need some of features (union in views, in particular) which are only
> available in 7.1-current. How insane would be to try it on production
> server? Are there known bugs that could cause loss of data or loss of
> updates? Or just newer features aren't polished yet?
On a production server? I wouldn't trust it with mission-critical data,
for sure. But that's more an issue of inadequate testing than that
there are known bugs.
If you try this, be sure to make frequent backups ...
> Also, where is cvs repository? Is there a CVSup access to it?
See http://www.postgresql.org/devel-corner/docs/postgres/cvs.htm
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2000-10-26 15:12:04 | Re: DBD::Pg::st execute failed: ERROR |
| Previous Message | Peter Eisentraut | 2000-10-26 15:03:17 | Re: Re: libpq needs -lsocket on UnixWare |