| From: | Raivo Rebane <raivore55(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Christoph Moench-Tegeder <cmt(at)burggraben(dot)net>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Binary large object processing problems |
| Date: | 2023-03-13 19:11:00 |
| Message-ID: | CAMH5fpsHY8pAzuY+gZ4JcO=fTvQAnDkHE2A3ZDv=NR_4gbkVNA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Ok, I will do that. ANd it works now in both way
Regards
Raivo
On Mon, Mar 13, 2023 at 6:18 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Raivo Rebane <raivore55(at)gmail(dot)com> writes:
> > Thank for answer, but I was also readed this manual and found there :
> > 35.3.2. Importing a Large Object
>
> You need to read the start of that section, which says
>
> All large object manipulation using these functions
> <emphasis>must</emphasis> take place within an SQL transaction block,
>
> As Christoph said, you're responsible for supplying a BEGIN and COMMIT
> around the call.
>
> regards, tom lane
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Israel Brewster | 2023-03-13 19:18:31 | Re: Properly handle OOM death? |
| Previous Message | Joe Conway | 2023-03-13 19:10:29 | Re: Properly handle OOM death? |