"David G. Johnston" writes:
> On Friday, November 20, 2020, Srinivasa T N wrote:
>> 2020-11-20 11:20:46.218 IST [38207] LOG: execute S_3: ROLLBACK
> If there was an error you would see an error message. Plus, PostgreSQL
> doesn’t just internally issue a rollback on its own. That said I’m not
>
On 20/11/2020 08:29, David G. Johnston wrote:
On Friday, November 20, 2020, Srinivasa T N
mailto:seen...@gmail.com>> wrote:
Hi,
I have the following in my log files:
2020-11-20 11:20:46.216 IST [38207] LOG: execute S_1/C_2: SELECT
"gid",encode(ST_AsBinary(ST_Simplify(ST_Force2D("shape"), 14.
On Friday, November 20, 2020, Srinivasa T N wrote:
> Hi,
>I have the following in my log files:
>
> 2020-11-20 11:20:46.216 IST [38207] LOG: execute S_1/C_2: SELECT
> "gid",encode(ST_AsBinary(ST_Simplify(ST_Force2D("shape"),
> 14.929338247701526, true)),'base64') as "shape" FROM
> "ami_smart_
Hi,
I have the following in my log files:
2020-11-20 11:20:46.216 IST [38207] LOG: execute S_1/C_2: SELECT
"gid",encode(ST_AsBinary(ST_Simplify(ST_Force2D("shape"),
14.929338247701526, true)),'base64') as "shape" FROM
"ami_smart_new"."aoi_boundary" WHERE ("sectioncode" IN ('4683', '4587') AND
"