Re: Savepoints in plpgsql

2024-08-05 Thread Олег Самойлов
On 12.07.2024 16:42, Tom Lane wrote: PL/pgSQL does not support savepoints (SAVEPOINT/ROLLBACK TO SAVEPOINT/RELEASE SAVEPOINT commands). Typical usage patterns for savepoints can be replaced by blocks with exception handlers (see 43.6.8). Under the hood, a block with exc

Re: Return codes for archive and restore commands

2018-12-03 Thread Олег Самойлов
> If you were to rewrite those paragraphs or make them more precise, how > would you actually shape your suggestions? I personally quite like the > current formulations, but I am rather used to it to be honest. > -- > Michael Yep, I am for make them more precise. Now this paragraphs describe Po

Re: Mistyped message severity

2018-12-26 Thread Олег Самойлов
Very interesting. I think the same for LOG and log messages? IMHO, it’s worth to add to the documentation. > 26 дек. 2018 г., в 20:31, Tom Lane написал(а): > > =?utf-8?q?PG_Doc_comments_form?= writes: >> Obviously wrongly pointed that for log messages a valid value is "INFO", but >> not "LOG"

Re: explanation for random_page_cost is outdated

2020-04-23 Thread Олег Самойлов
Yep. Unclear. What parameter is recommended for SSD? Lower? 3? 2? 1? Much better will be write: if you use SSD set 1. Олег > 19 марта 2020 г., в 23:56, Bruce Momjian написал(а): > > On Thu, Feb 27, 2020 at 02:48:44PM +, PG Doc comments form wrote: >> The following documentation comment ha

Re: explanation for random_page_cost is outdated

2020-04-27 Thread Олег Самойлов
Yes, I saw recommendations for 1.1 early, but why? Why such exactly precision number, why 1.1? Is here ever a theoretical or experimental prof? As for me, random_page_cost depended not only not characteristic of a storage device (hdd or ssd), but also on assumptions about how much of the databas

Re: Create a Foreign Table for PostgreSQL CSV Logs

2020-08-24 Thread Олег Самойлов
There must not be constraints at all. Constraints are needed to check incoming data to the table. But here table is read-only for database! So all your constraints is totally useless. > > could become: > > > > connection_from text check(connection_from ~ '^[^:]+:[0-9]+$) -- the host > > and > >

Re: Create a Foreign Table for PostgreSQL CSV Logs

2020-08-24 Thread Олег Самойлов
> 24 авг. 2020 г., в 18:07, Bruce Momjian написал(а): > > On Mon, Aug 24, 2020 at 07:40:49AM -0700, David G. Johnston wrote: >> On Mon, Aug 24, 2020 at 6:17 AM Олег Самойлов wrote: >> >>There must not be constraints at all. Constraints are needed to check

Re: Create a Foreign Table for PostgreSQL CSV Logs

2020-08-26 Thread Олег Самойлов
> 26 Aug 2020, в 09:24, Николай Чадаев написал(а): > > Thank You Oleg. > > A simple example is extremely important and necessary. > I will wait for this example. It's already exists. The idea was to add cross links to this.

Re: ^@ operator for text

2021-12-24 Thread Олег Самойлов
> 23 дек. 2021 г., в 18:18, Tom Lane написал(а): > > PG Doc comments form writes: >> In the new documentation >> https://www.postgresql.org/docs/14/functions-string.html >> you again lost information about ^@ operator for text and keep information >> about only function starts_with on which