From: | Surafel Temesgen <surafel3000(at)gmail(dot)com> |
---|---|
To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
Cc: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_dump multi VALUES INSERT |
Date: | 2019-02-18 13:33:53 |
Message-ID: | CALAY4q94Q5f6ecqRENp-wuoA0Ss6f72ag-8TPEKhpU+_Zuiwmg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Feb 2, 2019 at 11:26 AM Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> wrote:
> There is a test, that is good! Charater "." should be backslashed in the
> regexpr. I'd consider also introducing limit cases: empty table, empty
> columns by creating corresponding tables and using -t repeatedly
I see that there are already a test for zero column table in
test_fourth_table_zero_col
and if am not wrong table_index_stats is empty table
regards
Surafel
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2019-02-18 13:45:38 | Re: Incorrect visibility test function assigned to snapshot |
Previous Message | Alexey Kondratov | 2019-02-18 13:26:55 | Re: [Patch] pg_rewind: options to use restore_command from recovery.conf or command line |