Incremental backup in windows machine

good morning everyone. is it possible to do the incremental backup in windows machine? Thanks and regards Obireddy.G

Re: pg_dump insert column GENERATED

Ok, I'll take a look. I recreated the is_inside column yesterday, but it didn't make any difference. Uchet=# select attname, attgenerated from pg_attribute Uchet-# where attrelid = 'bpd.object'::regclass and attnum > 0; attname| attgenerated

Re: insert column monetary type ver 2

On 11/21/21 9:35 PM, Rob Sargent wrote: On Nov 21, 2021, at 8:21 PM, Ron wrote: Why then does the money type exist? At the very least, why isn't it deprecated? Some of us like it as an easy formatter trick for reports to_char() can do the same, no? -- Angular momentum makes the world go

Re: insert column monetary type ver 2

Thank you, I'm talking about this solution. вс, 21 нояб. 2021 г. в 22:46, vincent.vey...@libremen.org < vincent.vey...@libremen.org>: > On Sat, 20 Nov 2021 19:32:54 +0500 > Дмитрий Иванов wrote: > > > I saw it. I’m not tied down hard on this type. It's just that it exists > and > > I decided to

Re: insert column monetary type ver 2

> On Nov 21, 2021, at 8:21 PM, Ron wrote: > > Why then does the money type exist? At the very least, why isn't it > deprecated? Some of us like it as an easy formatter trick for reports > > -- > Angular momentum makes the world go 'round.

Re: insert column monetary type ver 2

On 11/21/21 8:43 PM, David G. Johnston wrote: On Sunday, November 21, 2021, Ron > wrote: On 11/21/21 7:33 PM, Adrian Klaver wrote: On 11/21/21 17:08, Ron wrote: On 11/21/21 10:27 AM, Tom Lane wrote: Ron

insert column monetary type ver 2

On Sunday, November 21, 2021, Ron wrote: > On 11/21/21 7:33 PM, Adrian Klaver wrote: > >> On 11/21/21 17:08, Ron wrote: >> >>> On 11/21/21 10:27 AM, Tom Lane wrote: >>> Ron writes: >>> >> The contrary argument is that people tend not to like "best guess" behavior when working

Re: insert column monetary type ver 2

On 11/21/21 7:33 PM, Adrian Klaver wrote: On 11/21/21 17:08, Ron wrote: On 11/21/21 10:27 AM, Tom Lane wrote: Ron writes: The contrary argument is that people tend not to like "best guess" behavior when working with monetary amounts. Best Guess is relative.  Breaking because of "ASCII

Re: insert column monetary type ver 2

On 11/21/21 17:08, Ron wrote: On 11/21/21 10:27 AM, Tom Lane wrote: Ron writes: The contrary argument is that people tend not to like "best guess" behavior when working with monetary amounts. Best Guess is relative.  Breaking because of "ASCII Space" instead of "narrow no-break space" is

Re: insert column monetary type ver 2

On 11/21/21 10:27 AM, Tom Lane wrote: Ron writes: On 11/20/21 11:01 AM, Tom Lane wrote: A quick lookup later, that's U+202F or "narrow no-break space". cash_in is picky about this, and won't take plain ASCII space as a substitute. Not sure if it should. It probably should, based on the

Re: Error when rewriting a query into multiple queries

On Friday, November 19, 2021, Huang Wang wrote: > Is there any way to do it on the server or it's better to do it in the > application? > Application; and for me at least modifying the server to do this is an extremely bad idea that goes against its fundamental design. David J.

Re: insert column monetary type ver 2

On Sat, 20 Nov 2021 19:32:54 +0500 Дмитрий Иванов wrote: > 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. > Consider storing integers; it's easy and fast, and all you need to do is display your numbers divided

Re: pg_dump insert column GENERATED

On 11/21/21 07:23, Дмитрий Иванов wrote: Yes and yes. I don't get regular results in my experiments. I filled in some of the tables this morning, but now I can't do it again. > INSERT INTO bpd.plan_calendar (create in version 12) > OK I can't do it again. You are going need to provide more

Re: insert column monetary type ver 2

Ron writes: > On 11/20/21 11:01 AM, Tom Lane wrote: >> A quick lookup later, that's U+202F or "narrow no-break space". >> cash_in is picky about this, and won't take plain ASCII space as >> a substitute. Not sure if it should. > It probably should, based on the Robustness Principle: "be

Re: pg_dump insert column GENERATED

=?UTF-8?B?0JTQvNC40YLRgNC40Lkg0JjQstCw0L3QvtCy?= writes: >> So did you do an ALTER TABLE ... GENERATED ALWAYS AS on bpg.object in >> the Postgres 12 version of the database? > I think you're right, I added later. Hmm, that's suggestive, but I tried making a table that way and still did not see

Re: pg_dump insert column GENERATED

Yes and yes. I don't get regular results in my experiments. I filled in some of the tables this morning, but now I can't do it again. > INSERT INTO bpd.plan_calendar (create in version 12) > OK I can't do it again. >If I am following the bpg.object table was originally created in >Postgres 10,