| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Marko Tiikkaja <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, robertmhaas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: regclass without error? |
| Date: | 2010-09-03 17:28:15 |
| Message-ID: | 1283534494-sup-8922@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from David Fetter's message of vie sep 03 10:21:00 -0400 2010:
> > How about using a SAVEPOINT before the cast? Wouldn't fail your
> > transaction..
>
> For unattended operation, there are some issues:
>
> * Generating appropriate SAVEPOINT names
> * Keeping track of same
> * Detecting errors
> * Issuing ROLLBACKs to the aforementioned SAVEPOINT
>
> None of this works super well for a bulk load.
Why do you need any of this? The logic is pretty simple:
SAVEPOINT my_savepoint;
select ...::regclass;
-- if it works
RELEASE my_savepoint;
-- if it fails
ROLLBACK TO my_savepoint;
RELEASE my_savepoint;
Granted, it's not super-performant ...
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2010-09-03 17:31:00 | Re: regclass without error? |
| Previous Message | Robert Haas | 2010-09-03 16:38:52 | Re: Interruptible sleeps (was Re: CommitFest 2009-07: Yay, Kevin! Thanks, reviewers!) |