Re: Data migration from postgres 8.4 to 9.4

2018-04-16 Thread Amitabh Kant
On Mon, Apr 16, 2018 at 12:33 PM, Akshay Ballarpure < akshay.ballarp...@tcs.com> wrote: > Hello, > I need help in using postgresql 8.4 data in postgres 9.4 version. Do I > need to run any tool to achieve the same? > > Steps i followed is ran postgresql 8.4 and 9.4, copied data from 8.4 > instance

Re: Is PostgreSQL SQL Database Command Syntax Similar to MySQL/MariaDB?

2020-03-31 Thread Amitabh Kant
On Tue, Mar 31, 2020 at 5:58 PM Turritopsis Dohrnii Teo En Ming < c...@teo-en-ming.com> wrote: > Does phpMyAdmin support PostgreSQL? > > > > On 2020-03-31 20:15, Ben Madin wrote: > > and \q works in MySQL, so it may not be different anyway :) > > > > On Tue, 31 Mar 2020 at 08:18, Tom Lane wrote:

Finding free time period on non-continous tstzrange field values

2022-11-30 Thread Amitabh Kant
Hi Given the following table, how do I find free time period. CREATE TABLE test_time_range ( id SERIAL PRIMARY KEY, time_range tstzrange); Insert into test_time_range(time_range) values('[2022-11-28 08:00:00, 2022-11-28 20:00:00]'); Insert into test_time_range(time_range) values('[2022-

Re: Finding free time period on non-continous tstzrange field values

2022-11-30 Thread Amitabh Kant
On Wed, Nov 30, 2022 at 7:20 PM Marcos Pegoraro wrote: > Given the following table, how do I find free time period. >> > > > https://www.crunchydata.com/blog/better-range-types-in-postgres-14-turning-100-lines-of-sql-into-3 > Thanks Marcos .. Had seen this earlier but somehow slipped my mind to

Re: Finding free time period on non-continous tstzrange field values

2022-11-30 Thread Amitabh Kant
On Wed, Nov 30, 2022 at 7:13 PM Amitabh Kant wrote: > Hi > > Given the following table, how do I find free time period. > > CREATE TABLE test_time_range ( > id SERIAL PRIMARY KEY, > time_range tstzrange); > > > Insert into test_time_range(time_range) values

Re: Finding free time period on non-continous tstzrange field values

2022-12-02 Thread Amitabh Kant
On Thu, Dec 1, 2022 at 7:59 PM Tom Lane wrote: > Amitabh Kant writes: > > I tried the following query : > > > SELECT tstzmultirange(tstzrange('2022-11-25 00:00:00', '2022-11-30 > > 00:00:00', '[]')) - > > range_agg(time_range) A

Re: Purging few months old data and vacuuming in production

2022-12-29 Thread Amitabh Kant
On Fri, Dec 30, 2022 at 12:09 PM Ranjith Paliyath wrote: > Hi, > > We have a PostgreSQL (slightly old version, something like - PostgreSQL > 11.2 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat > 4.8.5-36), 64-bit) production, where one particular table and its related 5 > t

Re: PgbackRest : Stanza creation fails on DB Server and Repo Server

2024-08-28 Thread Amitabh Kant
On Wed, Aug 28, 2024 at 8:00 PM David G. Johnston < david.g.johns...@gmail.com> wrote: > On Wednesday, August 28, 2024, KK CHN wrote: > >> >> and I have .pgpass in DB server as >> > > You assumed this mattered but I see no mention that pgBackRest consults > this file. > > It seems to require th

Re: timescaledb vs NULL vs pg_timeseries vs partman + pgcron + pg_ivm

2025-04-09 Thread Amitabh Kant
On Wed, Apr 9, 2025 at 11:50 AM Achilleas Mantzios - cloud < a.mantz...@cloud.gatewaynet.com> wrote: > > On 4/9/25 04:50, Amitabh Kant wrote: > > Thank you, I meant the paid/supported service not the community version. >> Which of the two do you use? >> >> >

Re: timescaledb vs NULL vs pg_timeseries vs partman + pgcron + pg_ivm

2025-04-08 Thread Amitabh Kant
On Tue, Apr 8, 2025 at 9:40 PM Achilleas Mantzios - cloud < a.mantz...@cloud.gatewaynet.com> wrote: > Hi > > timescaledb seemed mature, but also exotic, allow me the term. No way to > use native logical replication, shortage of options to run on premise or > self hosted, which leaves us with thos

Re: timescaledb vs NULL vs pg_timeseries vs partman + pgcron + pg_ivm

2025-04-08 Thread Amitabh Kant
On Tue, Apr 8, 2025 at 11:29 PM Achilleas Mantzios < a.mantz...@cloud.gatewaynet.com> wrote: > > On 8/4/25 20:37, Amitabh Kant wrote: > > On Tue, Apr 8, 2025 at 9:40 PM Achilleas Mantzios - cloud < > a.mantz...@cloud.gatewaynet.com> wrote: > >> Hi >> >