| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | adurugkar(at)xento(dot)com |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #11321: describe command is getting locked due to ALTER statement running on public table |
| Date: | 2014-09-01 17:01:54 |
| Message-ID: | 11249.1409590914@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
adurugkar(at)xento(dot)com writes:
> describe command is getting locked due to ALTER statement running on real
> table.
This isn't a bug IMO; if anything, it's a bug that the old implementation
of pg_get_indexdef didn't result in acquiring any lock. Without a lock,
you're at least at risk of printing garbage information, and I suspect
crashes were not out of the question.
> It was working fine on 9.3.4 version.
I rather doubt this behavior changed just in 9.3.5. That code got
rewritten during 9.3 development.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2014-09-01 20:00:41 | Re: Re: [BUGS] Re: BUG #9555: pg_dump for tables with inheritance recreates the table with the wrong order of columns |
| Previous Message | Haribabu Kommi | 2014-09-01 15:57:02 | Re: [BUGS] BUG #9652: inet types don't support min/max |