On 11/20/21 20:39, Дмитрий Иванов wrote:
Yes and yes.
I filled some tables with GENERATED fields as follows:
"C:\Program Files\PostgreSQL\12\bin\pg_dump" --file
"D:\UPLoad\-=PG-Uchet=-\Base\bpd.sql" --host "127.0.0.1" --port "5999"
--username "back" --no-password --verbose --format=p
--quote-a
I think I would love to discuss this topic, but my English won't allow it.
I understand this type is there but the best way to avoid mistakes when
working with it is not to work with it. thank you.
вс, 21 нояб. 2021 г. в 09:02, Ron :
> On 11/20/21 11:01 AM, Tom Lane wrote:
> > =?UTF-8?B?0JTQvNC40
Yes and yes.
I filled some tables with GENERATED fields as follows:
"C:\Program Files\PostgreSQL\12\bin\pg_dump" --file
"D:\UPLoad\-=PG-Uchet=-\Base\bpd.sql" --host "127.0.0.1" --port "5999"
--username "back" --no-password --verbose --format=p
--quote-all-identifiers --column-inserts --inserts --en
On 11/20/21 11:01 AM, Tom Lane wrote:
=?UTF-8?B?0JTQvNC40YLRgNC40Lkg0JjQstCw0L3QvtCy?= writes:
I can't figure out the problem. Digit group group separator causes an
insertion error, what should I do?
lc_monetary = 'ru_RU.UTF-8'
On my RHEL8 (moderately recent glibc) platform, that locale's
mon
On 11/20/21 17:11, Дмитрий Иванов wrote:
Yes and yes.
I ended up using the pg_dump of the receiving server.
sudo /usr/lib/postgresql/14/bin/pg_dump --file
"/home/dismay/uchet/Uchet.backup" --host "server" --port "5999"
--username "back" --no-password --verbose --format=c
--quote-all-identifie
Yes and yes.
I ended up using the pg_dump of the receiving server.
sudo /usr/lib/postgresql/14/bin/pg_dump --file
"/home/dismay/uchet/Uchet.backup" --host "server" --port "5999" --username
"back" --no-password --verbose --format=c --quote-all-identifiers --blobs
--column-inserts --inserts --creat
On 11/20/21 10:33, Дмитрий Иванов wrote:
I don't know.
sudo /usr/lib/postgresql/14/bin/pg_dump --file
"/home/dismay/uchet/Uchet.backup" --host "server" --port "5999"
--username "back" --no-password --verbose --format=c
--quote-all-identifiers --blobs --column-inserts --inserts --create
--dis
I don't know.
sudo /usr/lib/postgresql/14/bin/pg_dump --file
"/home/dismay/uchet/Uchet.backup" --host "server" --port "5999" --username
"back" --no-password --verbose --format=c --quote-all-identifiers --blobs
--column-inserts --inserts --create --disable-triggers --encoding="UTF8"
"Uchet"
I used
Ok, I see.
This is actually an interesting question. I don't understand which approach
to use. I am using pd_dump and pg_restore of the receiving server. It might
make sense to use pg_dump source, pg_restore sink
сб, 20 нояб. 2021 г. в 22:33, Tom Lane :
> Adrian Klaver writes:
> > On 11/20/21 0
Adrian Klaver writes:
> On 11/20/21 04:27, Дмитрий Иванов wrote:
>> Why does pg_dump generate an insertion script in the generated columns?
> Actually I think it should be DEFAULT.
It should be, and it is when I try this example. I get output like
--
-- Data for Name: object; Type: TABLE DATA
=?UTF-8?B?0JTQvNC40YLRgNC40Lkg0JjQstCw0L3QvtCy?= writes:
> I can't figure out the problem. Digit group group separator causes an
> insertion error, what should I do?
> lc_monetary = 'ru_RU.UTF-8'
On my RHEL8 (moderately recent glibc) platform, that locale's
mon_thousands_sep symbol is not a plai
On 11/20/21 04:27, Дмитрий Иванов wrote:
Good afternoon.
Why does pg_dump generate an insertion script in the generated columns?
This causes insertion errors.
PostgreSQL 14.1 (Debian 14.1-1.pgdg110+1) on x86_64-pc-linux-gnu,
compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
is_inside -
On 11/20/21 04:45, Дмитрий Иванов wrote:
Good afternoon.
Sorry about the first example.
I can't figure out the problem. Digit group group separator causes an
insertion error, what should I do?
lc_monetary = 'ru_RU.UTF-8'
Digit group group separator is a space.
Financial type format: 7,649.00 ₽
> On Nov 20, 2021, at 6:50 AM, Sanjay Minni wrote:
>
>
> In Postgres 12 and up, are there any default columns available which could be
> useful for tracking / auditing purposes ?
> e.g.
> - real user who entered / updated the data
> - timestamp when data was updated / entered
> where can i g
I saw it. I’m not tied down hard on this type. It's just that it exists and
I decided to include it in my development. Thanks.
сб, 20 нояб. 2021 г. в 19:18, Josef Šimánek :
> so 20. 11. 2021 v 13:45 odesílatel Дмитрий Иванов
> napsal:
> >
> > Good afternoon.
> > Sorry about the first example.
>
so 20. 11. 2021 v 13:45 odesílatel Дмитрий Иванов
napsal:
>
> Good afternoon.
> Sorry about the first example.
> I can't figure out the problem. Digit group group separator causes an
> insertion error, what should I do?
> lc_monetary = 'ru_RU.UTF-8'
> Digit group group separator is a space.
> Fi
In Postgres 12 and up, are there any default columns available which could
be useful for tracking / auditing purposes ?
e.g.
- real user who entered / updated the data
- timestamp when data was updated / entered
where can i get a list of such default columns (if any) - which could be
accessed easil
Good afternoon.
Sorry about the first example.
I can't figure out the problem. Digit group group separator causes an
insertion error, what should I do?
lc_monetary = 'ru_RU.UTF-8'
Digit group group separator is a space.
Financial type format: 7,649.00 ₽
DELETE FROM ONLY bpd.class_prop_user_small_v
Good afternoon.
Why does pg_dump generate an insertion script in the generated columns?
This causes insertion errors.
PostgreSQL 14.1 (Debian 14.1-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled
by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
is_inside - column should be excluded how to do it?
INSE
Good afternoon.
I can't figure out the problem. Digit group group separator causes an
insertion error, what should I do?
lc_monetary = 'ru_RU.UTF-8'
Digit group group separator is a space.
Financial type format: 7,649.00 ₽
DELETE FROM ONLY bpd.class_prop_user_small_val
WHERE id_class_prop = 74502;
20 matches
Mail list logo
