On Thu, Dec 27, 2018 at 05:52:14PM -0500, Ravi Krishna wrote:
> Unlogged tables are not stored in the catalog like a regular table. When
> it is converted to a logged table , the entire operation is logged (goes
> into wal logs) in one single transaction, blocking the entire table
> during the proc
On Thu, Dec 27, 2018, at 5:23 PM, Bhavin Gandhi wrote:
> Hello,
> I'm trying to understand for a given unlogged table of a specific size
> and # of rows, if I do "alter table" on it to convert it to logged
> table, is there a performance difference between 9.5, 9.6 and 10? in
> other words are the
Hello,
I'm trying to understand for a given unlogged table of a specific size and
# of rows, if I do "alter table" on it to convert it to logged table, is
there a performance difference between 9.5, 9.6 and 10? in other words are
there specific improvements in this area that may not be available in
On 2018-12-27 14:56:25 +0530, Sameer Thakur wrote:
> I am using Postgres 10.4
> I tried to insert ipv6 address '2001:db8:::::1.2.3.4'
> in Postgres (10.4) in an inet column. It is stored as
> 2001:db8:::::102:304.
No. It is *displayed* as "2001:db8::::66
Hello,
I am using Postgres 10.4
I tried to insert ipv6 address '2001:db8:::::1.2.3.4'
in Postgres (10.4) in an inet column. It is stored as
2001:db8:::::102:304.
Why is the IP stored differently?
Does the stored IP represent the same one being inserted?
Is this a kn
Hi!
I started a patch to address this limitation. [1]
[1]
https://www.postgresql.org/message-id/CAKLmikMN%2B0W79A7Wg4krK55cTLxb%3DTARdz2b%3Dvqp19ao6AAZjw%40mail.gmail.com
Mitar
On Mon, Dec 24, 2018 at 1:38 AM Mitar wrote:
>
> Hi!
>
> On Mon, Dec 24, 2018 at 1:31 AM George Neuner wrote:
> >
Hi!
FYI, I started working on also adding TEMPORARY materialized views. [1]
[1]
https://www.postgresql.org/message-id/CAKLmikOwqJx7J%3Dfg7VFcuk2OUjqLy%3DHZj_J5stY1x8X7%2B14g5g%40mail.gmail.com
UNLOGGED is still unsupported, but TEMPORARY materialized views do not
have the issue mentioned in the
