Продукты

О компании

Ресурсы

Мероприятия

Образование

...

Протестировать

Архив рассылок [pgsql-hackers]

29 августа 2018 г.

00:04Re: Would it be possible to have parallel archiving? Andrey Borodin

00:12some pg_dump query code simplification Peter Eisentraut

00:15Re: Would it be possible to have parallel archiving? David Steele

00:20Re: Would it be possible to have parallel archiving? Stephen Frost

00:43Re: some pg_dump query code simplification Tom Lane

00:44Re: Would it be possible to have parallel archiving? Michael Paquier

00:49Re: Some pgq table rewrite incompatibility with logical decoding? Tomas Vondra

00:56Re: some pg_dump query code simplification Stephen Frost

01:01Re: Some pgq table rewrite incompatibility with logical decoding? Tomas Vondra

01:05Re: some pg_dump query code simplification Tom Lane

01:10Re: some pg_dump query code simplification Stephen Frost

01:22Re: More parallel pg_dump bogosities Tom Lane

01:25Re: some pg_dump query code simplification Tom Lane

01:28Re: some pg_dump query code simplification Stephen Frost

02:03Re: Why hash OIDs? Thomas Munro

02:05Re: Why hash OIDs? Thomas Munro

02:24Re: Postmaster doesn't send SIGTERM to bgworker during fast shutdownwhen pmState == PM_STARTUP Michael Paquier

02:45Re: Why hash OIDs? Thomas Munro

03:02Re: Why hash OIDs? Tom Lane

03:17Re: Reopen logfile on SIGHUP Kyotaro HORIGUCHI

03:39Re: Copy function for logical replication slots Masahiko Sawada

04:34Re: BUG #15182: Canceling authentication due to timeout aka Denialof Service Attack Michael Paquier

05:04Re: Reopen logfile on SIGHUP Kyotaro HORIGUCHI

05:56Re: buildfarm: could not read block 3 in file "base/16384/2662":read only 0 of 8192 bytes Andres Freund

06:13Re: buildfarm: could not read block 3 in file "base/16384/2662":read only 0 of 8192 bytes Andres Freund

06:18Re: buildfarm: could not read block 3 in file "base/16384/2662": read only 0 of 8192 bytes Tom Lane

06:27Re: buildfarm: could not read block 3 in file "base/16384/2662":read only 0 of 8192 bytes Andres Freund

06:29Re: buildfarm: could not read block 3 in file "base/16384/2662":read only 0 of 8192 bytes Andres Freund

06:32Re: buildfarm: could not read block 3 in file "base/16384/2662": read only 0 of 8192 bytes Tom Lane

06:51Re: buildfarm: could not read block 3 in file "base/16384/2662":read only 0 of 8192 bytes Andres Freund

07:50Re: Refactor textToQualifiedNameList() Yugo Nagata

09:32Re: "Write amplification" is made worse by "getting tired" whileinserting into nbtree secondary indexes (Was: Why B-Tree suffix truncationmatters) Peter Eisentraut

10:09Re: Postmaster doesn't send SIGTERM to bgworker during fast shutdownwhen pmState == PM_STARTUP Alexander Kukushkin

10:28Re: Catalog corruption Mariel Cherkassky

10:32Re: [HACKERS] advanced partition matching algorithm forpartition-wise join Ashutosh Bapat

11:26Re: logical decoding: ABI break in 10.5 et al Christoph Berg

11:28Re: pg_verify_checksums -d option (was: Re: pg_verify_checksums -roption) Daniel Gustafsson

11:32A strange GiST error message or fillfactor of GiST build Kyotaro HORIGUCHI

11:37Re: buildfarm: could not read block 3 in file "base/16384/2662":read only 0 of 8192 bytes Andres Freund

11:38Re: Flexible configuration for full-text search Aleksandr Parfenov

12:01Re: Reopen logfile on SIGHUP Alexander Korotkov

12:09Re: pg_verify_checksums failure with hash indexes Amit Kapila

12:25Re: pg_verify_checksums failure with hash indexes Yugo Nagata

12:37PL/Python: Remove use of simple slicing API Peter Eisentraut

12:40Re: Expression errors with "FOR UPDATE" and postgres_fdw with partitionwise join enabled. Etsuro Fujita

13:00Re: pg_verify_checksums failure with hash indexes Yugo Nagata

13:09Re: pg_verify_checksums failure with hash indexes Dilip Kumar

13:13Use C99 designated initializers for some structs Peter Eisentraut

13:14Re: Use C99 designated initializers for some structs Peter Eisentraut

13:18Re: Stored procedures and out parameters Vladimir Sitnikov

13:31Re: pg_verify_checksums failure with hash indexes Amit Kapila

13:34Re: pg_verify_checksums failure with hash indexes Dilip Kumar

14:10Re: pg_verify_checksums failure with hash indexes Yugo Nagata

14:31Re: Catalog corruption Andrew Gierth

14:31pg_verify_checksums vs windows Amit Kapila

14:33Re: pg_verify_checksums -d option (was: Re: pg_verify_checksums -roption) Yugo Nagata

14:35Re: pg_verify_checksums vs windows Magnus Hagander

14:37Re: pg_verify_checksums -d option (was: Re: pg_verify_checksums -roption) Michael Banck

14:38Re: Two proposed modifications to the PostgreSQL FDW Etsuro Fujita

14:44Re: pg_verify_checksums vs windows Amit Kapila

14:46Re: pg_verify_checksums -d option (was: Re: pg_verify_checksums -r option) Magnus Hagander

14:47Re: pg_verify_checksums vs windows Magnus Hagander

15:06speeding up planning with partitions Amit Langote

15:09Re: pg_verify_checksums -d option (was: Re: pg_verify_checksums -roption) Yugo Nagata

15:46Re: some pg_dump query code simplification Andrew Dunstan

15:51Re: some pg_dump query code simplification Andrew Dunstan

16:08Re: some more error location support Peter Eisentraut

16:11Re: some more error location support Peter Eisentraut

16:24Re: Removing useless \. at the end of copy in pgbench Peter Eisentraut

16:27Re: Continue work on changes to recovery.conf API Peter Eisentraut

16:42Re: A strange GiST error message or fillfactor of GiST build Andrey Borodin

17:0110.5 but not 10.4: backend startup during reindex system: could notread block 0 in file "base/16400/..": read only 0 of 8192 bytes Justin Pryzby

17:04Is child process of postmaster able to access all the databases? Hubert Zhang

17:25Re: pg_verify_checksums -d option (was: Re: pg_verify_checksums -roption) Yugo Nagata

17:35Re: Removing useless \. at the end of copy in pgbench Fabien COELHO

17:39Re: some more error location support Fabien COELHO

17:41Re: Removing useless \. at the end of copy in pgbench Chapman Flack

17:45Re: Removing useless \. at the end of copy in pgbench Alvaro Herrera

17:54Re: some pg_dump query code simplification Peter Eisentraut

18:30Re: buildfarm: could not read block 3 in file "base/16384/2662": read only 0 of 8192 bytes Tom Lane

18:33Re: Is child process of postmaster able to access all the databases? Tom Lane

18:35Re: 10.5 but not 10.4: backend startup during reindex system: could not read block 0 in file "base/16400/..": read only 0 of 8192 bytes Tom Lane

18:43rare crash - FailedAssertion snapbuild.c Line: 580 Erik Rijkers

18:43Re: Continue work on changes to recovery.conf API Sergei Kornilov

18:59Re: Removing useless \. at the end of copy in pgbench Tom Lane

19:15Re: some pg_dump query code simplification Tom Lane

19:38Re: Something's busted in plpgsql composite-variable handling Jonathan S. Katz

19:56Re: buildfarm: could not read block 3 in file "base/16384/2662": read only 0 of 8192 bytes Tom Lane

20:38Re: FailedAssertion on partprune Robert Haas

20:45Re: Removing useless \. at the end of copy in pgbench Fabien COELHO

21:00Re: buildfarm: could not read block 3 in file "base/16384/2662": read only 0 of 8192 bytes Tom Lane

21:10Re: [HACKERS] proposal: schema variables Fabien COELHO

21:23Re: FailedAssertion on partprune Robert Haas

22:15Re: rare crash - FailedAssertion snapbuild.c Line: 580 Andres Freund

22:42Re: Removing useless \. at the end of copy in pgbench Fabien COELHO

22:45Re: buildfarm: could not read block 3 in file "base/16384/2662":read only 0 of 8192 bytes Andres Freund

22:48Re: Removing useless \. at the end of copy in pgbench Andres Freund

23:16Re: buildfarm: could not read block 3 in file "base/16384/2662":read only 0 of 8192 bytes Andres Freund

23:38Re: buildfarm: could not read block 3 in file "base/16384/2662": read only 0 of 8192 bytes Tom Lane

23:41Re: buildfarm: could not read block 3 in file "base/16384/2662": read only 0 of 8192 bytes Tom Lane

23:51Re: Use C99 designated initializers for some structs David Steele

23:56Re: Use C99 designated initializers for some structs Andres Freund

Ответы на вопросы