Hi ,
We are currently contemplating switching from MySQL to PostgreSQL, the main
attraction being the use of the TimescaleDB extension. Having done much of
the ground investigation there is one area of significant concern - the
storage requirement of PostgreSQL. Put simply, comparing like for like
On Mon, Apr 15, 2019 at 10:43 AM Ray Cheung <
ray.che...@silverpowersystems.com> wrote:
> Hi ,
>
> We are currently contemplating switching from MySQL to PostgreSQL, the main
> attraction being the use of the TimescaleDB extension. Having done much of
> the ground investigation there is one area o
On Mon, Apr 15, 2019 at 4:11 AM Takahashi, Ryohei
wrote:
> If application executes COMMIT statement and COMMIT failes because of
> PostgreSQL crash,
> it is unknown whether the transaction is really committed.
> Therefore, I think application should check the transaction is really
> committed af
Am 15.04.19 um 12:41 schrieb Francisco Olarte:
On Mon, Apr 15, 2019 at 4:11 AM Takahashi, Ryohei
wrote:
If application executes COMMIT statement and COMMIT failes because of
PostgreSQL crash,
it is unknown whether the transaction is really committed.
Therefore, I think application should ch
Hello all,
We are seeing an inexplicable behaviour when issuing an "UPDATE..RETURNING"
statement. I am unsure if it is a Postgres bug. Additional eyes-on would be
much appreicated.
When issuing the following statement we are seeing multiple rows UPDATE'd
despite the use of LIMIT 1 and despite
Joe Wildish writes:
> We are seeing an inexplicable behaviour when issuing an "UPDATE..RETURNING"
> statement. I am unsure if it is a Postgres bug. Additional eyes-on would be
> much appreicated.
> When issuing the following statement we are seeing multiple rows UPDATE'd
> despite the use of L
Hello All,
currently we are planning to migrate inheritance partitioning to
declarative partitioning by range values of int on pg10. But the key
values can contain null. I know that range partitioning does not allow
null values.
We are looking for workaround for this, that is create a list
par
I think it's better to had list partitioning of true/false based on
(int_key_column is null)
CREATE TABLE partitioned_table_name (like table_name) partition by list
((int_key_column is null));
On 16/04/2019 9:37, Soni wrote:
Hello All,
currently we are planning to migrate inheritance partition
Soni writes:
>> currently we are planning to migrate inheritance partitioning to
>> declarative partitioning by range values of int on pg10. But the key
>> values can contain null. I know that range partitioning does not allow
>> null values.
In v11 you could use a default partition ...
Hi Francisco and Andreas,
Thank you for your reply.
> So, if the library gives you an error ( "I have not received the commit
> confirmation" , not something like "commit failed" ), you will still
> need to test the data, if you can, to know how the server come back up.
Yes.
I want to know what
10 matches
Mail list logo
