"trailing junk after numeric literal at or near ""512"""

2024-12-23 Thread Olleg Samoylov
Hi all. I have PostgreSQL 16.6. The log files are attached as partitions by file_fdw to the SQL table. Common practice. But after the error message "trailing junk after numeric literal at or near ""512""" (vim -b view) was wrote, the reading all log was stopped with error from file_fdw: ERROR:

Re: Asynchronous Trigger?

2018-04-27 Thread Olleg Samoylov
Try to look at PGQ from SkyTools. On 2018-03-30 01:29, Cory Tucker wrote: Is it possible to have the execution of a trigger (or any function) not block the completion of the statement they are associated with?

Re: Locks analysis after-the-fact

2018-04-27 Thread Olleg Samoylov
On 2018-04-27 10:55, Olivier Macchioni wrote: > Does anyone have an idea on how to process in such a case? > Log statments too. :)

PostgreSQL 10.3 and Ubuntu

2018-03-05 Thread Olleg Samoylov
There is PostgreSQL 10.3 already. I have Ubuntu 17.10 (artful) and there is not a pgdg repository for it. There is PostgreSQL 10.3 in 16.04 LTS (xenial) pgdg repository, but such packages can't be installed on 17.10 (artful) Ubuntu. And there is zesty-pgdg (for 17.04 Ubuntu), works fine for me

Re: Using random() in update produces same random value for all

2018-01-23 Thread Olleg Samoylov
On 2018-01-22 23:15, Tom Lane wrote: > > It is honored as volatile: it will be re-evaluated every time the > sub-select is re-evaluated. It's just that there's no cause to > re-evaluate the sub-select. > > I poked through the SQL standard to see if it spells out the semantics > of uncorrelated sub

Re: Using random() in update produces same random value for all

2018-01-22 Thread Olleg Samoylov
Yep, interesting.  Checked with PostgreSQL 10.1. => select *,random() from generate_series(1,10);  generate_series |  random -+---    1 | 0.308531506918371    2 | 0.126279713585973    3 | 0.984668150078505    4