| From: | David Welton <davidw(at)dedasys(dot)com> |
|---|---|
| To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
| Cc: | Bradley McCune <bradley(dot)mccune(at)noaa(dot)gov>, Paul Tilles <paul(dot)tilles(at)noaa(dot)gov>, Postgres general mailing list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: V8.4 TOAST table problem |
| Date: | 2013-07-15 08:33:35 |
| Message-ID: | CA+b9R_v16FxwdLXe+Ti4jP6gZ53Q+rhQ0U90a3GQTrQxRJUevw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
I think I could write a script to do something similar to what is
happening if anyone is interested. I'd want some direction as to the
best way to handle this though: it'd be easier for me to script it as
Rails code because that's what the app is. Perhaps from that we can
get the generated SQL so as to make it easier for others to deal with.
The operation itself is basically:
* Extract a value from a row of a table that is stored as a bytea.
* Unmarshall it into a Ruby object.
* Add to that Ruby object.
* update the row and set the value by marshalling the Ruby object.
I suspect that the actual value isn't terribly relevant, and they
how's and why's of what it is like it is are best left for a different
discussion.
--
David N. Welton
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Luca Ferrari | 2013-07-15 08:44:09 | Re: |
| Previous Message | Vincenzo Romano | 2013-07-15 06:33:02 | Re: |