This report: http://archives.postgresql.org/pgsql-general/2008-06/msg00208.php shows that there is a nasty oversight in my patch of awhile back: http://archives.postgresql.org/pgsql-committers/2008-01/msg00081.php which might cause pg_dump output to fail to reload. This is a regression compared to the current releases in the pre-8.2 branches. Accordingly, core has determined that it is inadvisable to release the current code on Monday as was previously announced. Although the planned fix is quite simple, we will push the release date out a few days to give the packagers adequate time to do their work. (The exact new release date isn't determined yet.) Since the updated tarballs were already spun and might have been downloaded by a few people, we will generate new ones with new version numbers (8.3.3, etc) to avoid confusion. Sorry about that :-( regards, tom lane
I wrote:
> (The exact new release date isn't determined yet.)
Just FYI, the agreed plan is to slip the release schedule 3 days;
public announcement will be Thursday not Monday.
regards, tom lane
Сайт использует файлы cookie для корректной работы и повышения удобства. Нажимая кнопку «Принять» или продолжая пользоваться сайтом, вы соглашаетесь на их использование в соответствии с Политикой в отношении обработки cookie ООО «ППГ», в том числе на передачу данных из файлов cookie сторонним статистическим и рекламным службам. Вы можете управлять настройками cookie через параметры вашего браузера