Re: 20220221-Clarification regarding PostgeSQL DB backup

Hi Karthick In that case, your are options are: 1. Continuous WAL Archiving This is "like" using diff backups, but not quite the same. OR 2. Use a 3rd party app, for example Barman or pgBackRest

RE: 20220221-Clarification regarding PostgeSQL DB backup

Hi ~~Na-iem Dollie, Thanks for your reply, In SQL Server there is an option to take Full backup and Differential Backup for a particular database. Like that, we need to take the differential Backup in PostgreSQL. This is my primary need. Thanks, Karthick Ramu From: Daevo

Re: 20220221-Clarification regarding PostgeSQL DB backup

On 2/20/22 10:59 PM, Techsupport wrote: Hi Team, ** We have used PG_DUMP to take backup of particular database from the PostgreSQL Server. It takes too long to restore the databases , which has  Half Billion records (almost 8 Hour) My primary need is to make the Differential and Incremental

Re: 20220221-Clarification regarding PostgeSQL DB backup

Hi Karthick I'm a little rusty on PG (it's been about a decade since I last worked intensely with it), but I seem to remember that restoring with indexes can be very slow. The faster approach is to restore *without* indexes, and then create the indexes once the data restore is complete. My knowle

20220221-Clarification regarding PostgeSQL DB backup

Hi Team, We have used PG_DUMP to take backup of particular database from the PostgreSQL Server. It takes too long to restore the databases , which has Half Billion records (almost 8 Hour) My primary need is to make the Differential and Incremental backup on the Windows Serv

Re: Strange results when casting string to double

Carsten Klein writes: > Prior to restarting, I've implemented my own Python based versions of both > int fegetround(void); > int fesetround(int rounding_mode integer); Ah, good idea! > With those, I was able to proof, that actually the "wrong" rounding mode > FE_DOWNWARD (0x400) > was in effect

Re: Additional accessors via the Extension API ?

Julien Rouhaud writes: > On Sun, Feb 20, 2022 at 12:31:22PM +0200, Markur Sens wrote: >> Is this documented & expected behavior or it’s just happens to work? > I don't think it's documented but it's an expected behavior, see > https://github.com/postgres/postgres/blob/master/src/backend/parser/pa

Re: Strange results when casting string to double

On 19.02.2022 20:34 Tom Lane wrote: Per grep, there is no call of fesetround() in the Postgres source tree. I'm not sure offhand whether libc exposes any other APIs that could change the rounding mode, but I am quite sure that we wouldn't be intentionally changing it anywhere. The OS would

Re: Additional accessors via the Extension API ?

> On 20 Feb 2022, at 12:35 PM, Julien Rouhaud wrote: > > On Sun, Feb 20, 2022 at 12:31:22PM +0200, Markur Sens wrote: >>> >>> Maybe you could rely on some old grammar hack to have something a bit >>> similar, >>> as (expr).funcname is an alias for funcname(expr). For instance: >> >> Is this

Re: Additional accessors via the Extension API ?

On Sun, Feb 20, 2022 at 12:31:22PM +0200, Markur Sens wrote: > > > > Maybe you could rely on some old grammar hack to have something a bit > > similar, > > as (expr).funcname is an alias for funcname(expr). For instance: > > Is this documented & expected behavior or it’s just happens to work? I

Re: Additional accessors via the Extension API ?

> On 20 Feb 2022, at 12:12 PM, Julien Rouhaud wrote: > > Hi, > > On Sun, Feb 20, 2022 at 08:07:20AM +0200, Markur Sens wrote: >> Suppose I have defined an additional type in a PG extension. >> >> Is it possible to add custom accessors to that type -much like jsonb does- >> but use an API/ho

Re: Additional accessors via the Extension API ?

Hi, On Sun, Feb 20, 2022 at 08:07:20AM +0200, Markur Sens wrote: > Suppose I have defined an additional type in a PG extension. > > Is it possible to add custom accessors to that type -much like jsonb does- > but use an API/hook without touching the core PG grammar & parser? Unfortunately no. >

Aw: Additional accessors via the Extension API ?

> Suppose I have defined an additional type in a PG extension. > > Is it possible to add custom accessors to that type -much like jsonb does- > but use an API/hook without touching the core PG grammar & parser? > > Hypothetical Examples: > > Assuming I have a TextFile type I’d like to implem