| From: | Geoff Winkless <pgsqladmin(at)geoff(dot)dj> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Transactional-DDL DROP/CREATE TABLE |
| Date: | 2016-10-10 10:24:48 |
| Message-ID: | CAEzk6ff+q-jCOJV05LueDKAe5Nb8VEcUjiJeTqCASC6r5H4xZA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 6 October 2016 at 18:25, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:
> I do not see sarcasm, I see someone trying to work through what is a complex
> scenario.
When someone talks about things "magically working as you think it
should" I see sarcasm. Perhaps I misread, in which case I apologise.
>> _As far as the transaction is concerned_, after the command the table
>
> What command?
The "DROP TABLE IF EXISTS" command.
>> But that's NOT what this function is for. It's designed to remove a
>> table without producing an error if it didn't exist. The fact that its
>> RETURN value is "DROP TABLE", whether it dropped or not, shows this.
>
> What function?
I'm mixing up terminologies (statement, not function). I'm still
talking about "DROP TABLE IF EXISTS" here.
Geoff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Geoff Winkless | 2016-10-10 10:31:58 | Re: Transactional-DDL DROP/CREATE TABLE |
| Previous Message | Pavel Stehule | 2016-10-10 04:29:09 | Re: HA Cluster Solution? |