| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Дмитрий Сергеевич <dima(at)chelarsenal(dot)ru>, Devrim Gündüz <devrim(at)gunduz(dot)org> |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: Danger |
| Date: | 2017-05-30 01:26:44 |
| Message-ID: | CAKFQuwZk+HPUGU0Bt=A6_UkUf=ODVQq_xEJ1cHnpnrBH2sk9FQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, May 29, 2017 at 1:58 PM, Дмитрий Сергеевич <dima(at)chelarsenal(dot)ru>
wrote:
> Why in repo rhel6 include rhel7??? This update error.
>
Relaying the same message posted to the other bug threads on this topic.
The non-form submission and generic title of danger made this one easy to
miss.
"""
:-( This happened today, while I was unifying build instances :( This
affected
all RHEL 6 - x86_64 installations.
Fixed master repo by restoring from the backups. They will sync to
download.postgresql.org in next 10-15 mins.
Can you please let me know if you see more issues?
Apologies for the inconvenience.
"""
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | achill | 2017-05-30 06:55:58 | BUG #14679: Inconsistent/wrong behavior of pg_trigger_depth when used with DEFERRED CONSTRAINTS |
| Previous Message | Amit Langote | 2017-05-30 01:20:35 | Re: BUG #14671: INSERT..RETURNING on partitioned table |