Re: permission denied for large object 200936761

From: Andrus <kobruleht2(at)hot(dot)ee>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-general(at)postgresql(dot)org
Subject: Re: permission denied for large object 200936761
Date: 2021-02-02 09:35:00
Message-ID: 00d9c25a-8336-adbd-45da-37c946edb9a4@hot.ee
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi!
>
> I don't suppose this was done in a structured way that could be gone
> back over?
>
Accidently  '200936767'::lo cast was issued :

INSERT INTO report ( ...  ) values (.. , '200936767'::lo, ... )

server throws error   type "lo" does not exist for this.

Maybe this causes orphan large object creation by server or by odbc
driver. How to fix this ?

report table shoud not have lo type columns. No idea why this cast is
generated using psqlodbc

Andrus.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Laurenz Albe 2021-02-02 09:37:38 Re: permission denied for large object 200936761
Previous Message Andrus 2021-02-02 08:59:19 Re: permission denied for large object 200936761