| From: | sri harsha <sriharsha9992(at)gmail(dot)com> |
|---|---|
| To: | John R Pierce <pierce(at)hogranch(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Information regarding Table-Locks |
| Date: | 2015-01-16 05:24:35 |
| Message-ID: | CAP6OGLHBDYEMzCWLDV6BuqiVv-27aj+sk6J1d80fohXFRe89CA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi John.
What if my query was INSERT INTO Postgres_Table_A SELECT * FROM
Postgres_Table_B ?? What are the locks given for the two tables ??
--Harsha
On Fri, Jan 16, 2015 at 10:50 AM, John R Pierce <pierce(at)hogranch(dot)com> wrote:
> On 1/15/2015 9:14 PM, sri harsha wrote:
>
>> What kind of lock will the second table will be in ?
>>
>
> I suspect that depends on what FOREIGN_TABLE is connected to.
>
>
>
> --
> john r pierce 37N 122W
> somewhere on the middle of the left coast
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | M Tarkeshwar Rao | 2015-01-16 05:38:35 | Re: can you have any idea about toast missing chunk issu resolution |
| Previous Message | John R Pierce | 2015-01-16 05:20:21 | Re: Information regarding Table-Locks |