On Mon, Nov 11, 2024 at 12:41 AM yudhi s wrote:
> So it means it will ensure no duplication happens for ID values, but still we
> are seeing "duplicate key" error. So what is the possible reason here or are
> we encountering any buggy behaviour here?
MERGE doesn't actually make any promises abo
On Mon, Nov 11, 2024 at 1:57 PM Achilleas Mantzios - cloud <
a.mantz...@cloud.gatewaynet.com> wrote:
>
> > WITH source_data (col1, col2, col3.col29) AS (VALUES ($1,
> > $2::date, $3::timestamptz, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13,
> > $14, $15, $16, $17, $18, $19, $20, $21, $22, $23,
On 11/10/24 07:11, JOLAPARA Urvi (SAFRAN) wrote:
C2 - Confidential
Hello Team,
I am from Application Packaging team. we have created the package of
PostgreSQL 17.0-1 Application.
You are going to need to provide more detail on the package creation
process.
We have used the command line
C2 - Confidential
Hello Team,
I am from Application Packaging team. we have created the package of PostgreSQL
17.0-1 Application.
We have used the command line parameter for installation is this :
"postgresql-17.0-1-windows-x64.exe--mode unattended --unattendedmodeui none
--optionfile C:\Temp
CC
On Mon, Nov 11, 2024 at 09:28 Greg Sabino Mullane
wrote:
> Some of those requirements are vague, but yes, Patroni should probably be
> the first approach you look at. If the second datacenter is just for
> redundancy, then a simple setup would be:
>
> DCA (data center A):
> Postgres server 1
Some of those requirements are vague, but yes, Patroni should probably be
the first approach you look at. If the second datacenter is just for
redundancy, then a simple setup would be:
DCA (data center A):
Postgres server 1
Postgres server 2
DCB:
Postgres server 3 (set no_failover: true)
You wil
Hi Postgres Community,
I wanted to ask about support for temporal tables as defined in the SQL:2011
standard. Right now, I know that we can get similar functionality using
extensions like pg_temporal, which has been really useful. But for those of us
running PostgreSQL on managed platforms like
Hello Kirill
On 2024-Nov-11, Kirill Reshke wrote:
> I was exploring the PostgreSQL parser and discovered a very
> interesting feature. Users can create schema along with schema objects
> in single SQL.
Yeah, it's pretty cool.
> Support for materialized views began in 9.3. Perhaps, then, this is
On 11/11/24 07:40, yudhi s wrote:
We have a merge query as below for a partition table which is range
partitioned on a truncated date column 'part_date'. And the only
unique key in this table is a composite primary key on (id,
part_date). And this merge queries ON condition is based on one of
Hi!
I was exploring the PostgreSQL parser and discovered a very
interesting feature. Users can create schema along with schema objects
in single SQL.
So, for example
```
db1=# create schema shshshsh create table t1(i int) create view v1 as
select * from t1;
CREATE SCHEMA
```
works.
But `create sc
10 matches
Mail list logo
