Re: [PATCH] Add --syntax to postgres for SQL syntax checking

st 15. 5. 2024 v 20:39 odesílatel Tom Lane napsal: > > =?UTF-8?B?Sm9zZWYgxaBpbcOhbmVr?= writes: > > I'm not sure everyone in this thread understands the reason for this > > patch, which is clearly my fault, since I have failed to explain. Main > > idea is to make a tool to validate query can be

Re: [PATCH] Add --syntax to postgres for SQL syntax checking

pá 15. 12. 2023 v 15:50 odesílatel Tom Lane napsal: > > Laurenz Albe writes: > > On Fri, 2023-12-15 at 13:21 +0100, Josef Šimánek wrote: > >> Inspired by Simon Riggs' keynote talk at PGCounf.eu 2023 sharing list > >> of ideas for PostgreSQL > >> (https:

Re: [PATCH] Add --syntax to postgres for SQL syntax checking

st 15. 5. 2024 v 19:43 odesílatel Robert Haas napsal: > > On Sun, Feb 25, 2024 at 5:24 PM Tomas Vondra > wrote: > > I think there's about 0% chance we'd add this to "postgres" binary. > > Several people have taken this position, so I'm going to mark > https://commitfest.postgresql.org/48/4704/

Re: [PATCH] Add --syntax to postgres for SQL syntax checking

po 26. 2. 2024 v 8:20 odesílatel Jelte Fennema-Nio napsal: > > On Sun, 25 Feb 2024 at 23:34, Josef Šimánek wrote: > > Exposing parser to frontend tools makes no sense to me > > Not everyone seems to agree with that, it's actually already done by > Lukas from pganalyz

Re: [PATCH] Add --syntax to postgres for SQL syntax checking

ne 25. 2. 2024 v 23:24 odesílatel Tomas Vondra napsal: > > > > On 12/15/23 16:38, Josef Šimánek wrote: > > pá 15. 12. 2023 v 16:32 odesílatel David G. Johnston > > napsal: > >> > >> On Fri, Dec 15, 2023 at 8:20 AM Josef Šimánek > >> wrote: &

Re: [PATCH] Add --syntax to postgres for SQL syntax checking

pá 15. 12. 2023 v 16:32 odesílatel David G. Johnston napsal: > > On Fri, Dec 15, 2023 at 8:20 AM Josef Šimánek wrote: >> >> (parser is not available >> in public APIs of postgres_fe.h or libpq). > > > What about building "libpg" that does expose and

Re: [PATCH] Add --syntax to postgres for SQL syntax checking

pá 15. 12. 2023 v 16:16 odesílatel David G. Johnston napsal: > > On Fri, Dec 15, 2023 at 8:05 AM Josef Šimánek wrote: >> >> pá 15. 12. 2023 v 15:50 odesílatel Tom Lane napsal: >> > >> > Laurenz Albe writes: >> > > On Fri, 2023-12-15 at 13

Re: [PATCH] Add --syntax to postgres for SQL syntax checking

pá 15. 12. 2023 v 15:50 odesílatel Tom Lane napsal: > > Laurenz Albe writes: > > On Fri, 2023-12-15 at 13:21 +0100, Josef Šimánek wrote: > >> Inspired by Simon Riggs' keynote talk at PGCounf.eu 2023 sharing list > >> of ideas for PostgreSQL > >> (https:

Re: [PATCH] Add --syntax to postgres for SQL syntax checking

Dne pá 15. 12. 2023 14:09 uživatel Laurenz Albe napsal: > On Fri, 2023-12-15 at 13:21 +0100, Josef Šimánek wrote: > > Inspired by Simon Riggs' keynote talk at PGCounf.eu 2023 sharing list > > of ideas for PostgreSQL > > (https://riggs.business/blog/f/postgresql-todo-

[PATCH] Add --syntax to postgres for SQL syntax checking

Hello! Inspired by Simon Riggs' keynote talk at PGCounf.eu 2023 sharing list of ideas for PostgreSQL (https://riggs.business/blog/f/postgresql-todo-2023), I have crafted a quick patch to do SQL syntax validation. It is also heavily inspired by the "ruby -c" command, useful to check syntax of

Re: GTIN14 support for contrib/isn

čt 8. 6. 2023 v 17:20 odesílatel Michael Kefeder napsal: > > > Am 15.03.19 um 17:27 schrieb Tom Lane: > > Michael Kefeder writes: > >> For a project of ours we need GTIN14 data type support. > > > > Hm, what is that and where would a reviewer find the specification for it? > > > specs are from

Re: Ignoring BRIN for HOT updates (was: -udpates seems broken)

po 20. 3. 2023 v 11:24 odesílatel Matthias van de Meent napsal: > > On Mon, 20 Mar 2023 at 11:11, Tomas Vondra > wrote: > > > > On 3/14/23 15:41, Matthias van de Meent wrote: > > > On Tue, 14 Mar 2023 at 14:49, Tomas Vondra > > > wrote: > > >> > > >>> ... > > > > > >> If you agree with these

Re: How about a psql backslash command to show GUCs?

st 6. 4. 2022 v 19:49 odesílatel Tom Lane napsal: > > It's not difficult to get psql to show you the current value > of a single GUC --- "SHOW" does that fine, and it has tab > completion support for the GUC name. However, I very often > find myself resorting to the much more tedious > > select

Re: faulty link

čt 10. 2. 2022 v 15:35 odesílatel Erik Rijkers napsal: > > The provided link >https://www.postgresql.org/docs/release/ > > leads to >https://www.postgresql.org/docs/release/14.2/ > > which gives 'Not Found' for me (Netherlands) Thinking about that again, the 14.2 release just happened.

Re: faulty link

It works well here (Czech republic). čt 10. 2. 2022 v 15:35 odesílatel Erik Rijkers napsal: > > The provided link >https://www.postgresql.org/docs/release/ > > leads to >https://www.postgresql.org/docs/release/14.2/ > > which gives 'Not Found' for me (Netherlands) > > > At least one

Re: New developer papercut - Makefile references INSTALL

pá 21. 1. 2022 v 16:31 odesílatel Tom Lane napsal: > > =?UTF-8?B?Sm9zZWYgxaBpbcOhbmVr?= writes: > > There is README.git explaining this. README itself is meant to be used > > for distributed source code. You can generate INSTALL locally for > > example by running make dist (INSTALL will be

Re: New developer papercut - Makefile references INSTALL

pá 21. 1. 2022 v 1:29 odesílatel samay sharma napsal: > > > > On Wed, Jan 19, 2022 at 4:58 PM Tim McNamara wrote: >> >> Hello, >> >> I encountered a minor road bump when checking out the pg source today. The >> Makefile's all target includes the following help message if GNUmakefile >> isn't

Re: Add Boolean node

po 27. 12. 2021 v 16:10 odesílatel Alvaro Herrera napsal: > > On 2021-Dec-27, Peter Eisentraut wrote: > > > This patch adds a new node type Boolean, to go alongside the "value" nodes > > Integer, Float, String, etc. This seems appropriate given that Boolean > > values are a fundamental part of

Re: [PATCH] Don't block HOT update by BRIN index

út 30. 11. 2021 v 20:11 odesílatel Tomas Vondra napsal: > > OK, > > I've polished the last version of the patch a bit (added a regression > test with update of attribute in index predicate and docs about the new > flag into indexam.sgml) and pushed. Thanks a lot for taking over this, improving

Re: [RFC] building postgres with meson

čt 14. 10. 2021 v 19:24 odesílatel Andres Freund napsal: > > Hi, > > On 2021-10-14 10:29:42 -0300, Alvaro Herrera wrote: > > On 2021-Oct-14, Josef Šimánek wrote: > > > > > I'm using Fedora 34 and I still see perl-Opcode.x86_64 as a separate > > &

Re: [RFC] building postgres with meson

čt 14. 10. 2021 v 15:32 odesílatel Dagfinn Ilmari Mannsåker napsal: > > Josef Šimánek writes: > > > čt 14. 10. 2021 v 15:14 odesílatel Dagfinn Ilmari Mannsåker > > napsal: > >> > >> Josef Šimánek writes: > >> > >> > The onl

Re: [PATCH] Proposal for HIDDEN/INVISIBLE column

čt 14. 10. 2021 v 13:17 odesílatel Gilles Darold napsal: > > Hi, > > > Here is a proposal to implement HIDDEN columns feature in PostgreSQL. > > The user defined columns are always visible in the PostgreSQL. If user > wants to hide some column(s) from a SELECT * returned values then the > hidden

Re: [RFC] building postgres with meson

čt 14. 10. 2021 v 15:14 odesílatel Dagfinn Ilmari Mannsåker napsal: > > Josef Šimánek writes: > > > The only problem I do have currently is auto-detection of perl. I'm > > getting error related to missing "Opcode.pm". PERL is autodetected and > > enabled (htt

Re: [RFC] building postgres with meson

st 13. 10. 2021 v 1:54 odesílatel Andres Freund napsal: > > Hi, > > On 2021-10-13 01:19:27 +0200, Josef Šimánek wrote: > > I tried to clean and start from scratch, but I'm getting different > > error probably related to wrongly configured JIT (LLVM wasn't found > > d

Re: [RFC] building postgres with meson

út 12. 10. 2021 v 19:17 odesílatel Andres Freund napsal: > > Hi, > > On 2021-10-12 17:21:50 +0200, Josef Šimánek wrote: > > > # build (uses automatically as many cores as available) > > > ninja > > > > I'm getting errors at this step. You can find my o

Re: [RFC] building postgres with meson

. út 12. 10. 2021 v 10:37 odesílatel Andres Freund napsal: > > Hi, > > For the last year or so I've on and off tinkered with $subject. I think > it's in a state worth sharing now. First, let's look at a little > comparison. > > My workstation: > > non-cached configure: > current:11.80s

Re: [PATCH] Don't block HOT update by BRIN index

po 4. 10. 2021 v 16:17 odesílatel Tomas Vondra napsal: > > Hi, > > I took a look at this patch again to see if I can get it polished and > fixed. Per the discussion, I've removed the rd_indexattr list and > replaced it with a simple flag. While doing so, I noticed a couple of > places that should

Re: Git revision in tarballs

čt 15. 7. 2021 v 10:33 odesílatel Magnus Hagander napsal: > > I think it'd be useful to be able to identify exactly which git commit > was used to produce a tarball. This would be especially useful when > downloading snapshot tarballs where that's not entirely clear, but can > also be used to

Re: [PATCH] Don't block HOT update by BRIN index

po 12. 7. 2021 v 23:15 odesílatel Tomas Vondra napsal: > > > > On 7/12/21 11:02 PM, Alvaro Herrera wrote: > > On 2021-Jul-12, Josef Šimánek wrote: > > > >>> 2) Do we actually need to calculate and store hotblockingattrs > >>> separately in Relati

Re: [PATCH] Don't block HOT update by BRIN index

po 12. 7. 2021 v 22:31 odesílatel Tomas Vondra napsal: > > On 6/30/21 1:43 AM, Josef Šimánek wrote: > > st 30. 6. 2021 v 1:20 odesílatel Tomas Vondra > > napsal: > >> > >> > >> > >> On 6/30/21 12:53 AM, Josef Šimánek wrote: > >>

Re: [PATCH] Don't block HOT update by BRIN index

st 30. 6. 2021 v 1:20 odesílatel Tomas Vondra napsal: > > > > On 6/30/21 12:53 AM, Josef Šimánek wrote: > > st 30. 6. 2021 v 0:31 odesílatel Josef Šimánek > > napsal: > >> > >> Hello! > >> > >> Tomáš Vondra has shared a few ideas t

Re: [PATCH] Don't block HOT update by BRIN index

st 30. 6. 2021 v 0:31 odesílatel Josef Šimánek napsal: > > Hello! > > Tomáš Vondra has shared a few ideas to improve BRIN index in czech > PostgreSQL mail list some time ago [1 , in czech only]. This is first > try to implement one of those ideas. > > Currently BRIN inde

[PATCH] Don't block HOT update by BRIN index

Hello! Tomáš Vondra has shared a few ideas to improve BRIN index in czech PostgreSQL mail list some time ago [1 , in czech only]. This is first try to implement one of those ideas. Currently BRIN index blocks HOT update even it is not linked tuples directly. I'm attaching the initial patch

Re: Improvements and additions to COPY progress reporting

út 9. 3. 2021 v 6:34 odesílatel Michael Paquier napsal: > > On Mon, Mar 08, 2021 at 05:33:40PM +0100, Matthias van de Meent wrote: > > Seems reasonable. PFA updated patches. I've renamed the previous 0003 > > to 0002 to keep git-format-patch easy. > > Thanks for updating the patch. 0001 has been

Re: Improvements and additions to COPY progress reporting

čt 4. 3. 2021 v 12:32 odesílatel Matthias van de Meent napsal: > > On Thu, 4 Mar 2021 at 11:38, Michael Paquier wrote: > > > > On Thu, Mar 04, 2021 at 12:16:17PM +0530, Bharath Rupireddy wrote: > > > IMO, the phrasing proposed by Justin upthread looks good. It's like this: > > > > > > > +

Re: Improvements and additions to COPY progress reporting

so 20. 2. 2021 v 7:09 odesílatel Bharath Rupireddy napsal: > > On Fri, Feb 19, 2021 at 2:34 AM Tomas Vondra > wrote: > > > On Mon, 15 Feb 2021 at 17:07, Tomas Vondra > > > wrote: > > >> > > >> - The blocks in copyfrom.cc/copyto.c should be reworked - I don't think > > >> we do this in our

Re: Improvements and additions to COPY progress reporting

rrent commitfest. > > > > > > See https://commitfest.postgresql.org/32/2977/ > > > > > > On Tue, 9 Feb 2021 at 12:53, Josef Šimánek > > > wrote: > > > > > > > > OK, would you mind to integrate my regression test initial patch as > > > >

Re: Improvements and additions to COPY progress reporting

út 9. 2. 2021 v 12:51 odesílatel 0010203112132233 napsal: > > On Tue, 9 Feb 2021 at 09:32, Josef Šimánek wrote: > > > > po 8. 2. 2021 v 19:35 odesílatel Matthias van de Meent > > napsal: > > > Lastly, 0005 adds 'io_target' to the reported information, th

Re: Improvements and additions to COPY progress reporting

po 8. 2. 2021 v 19:35 odesílatel Matthias van de Meent napsal: > > Hi, > > With [0] we got COPY progress reporting. Before the column names of > this newly added view are effectively set in stone with the release of > pg14, I propose the following set of relatively small patches. These > are v2,

Re: Improvements and additions to COPY progress reporting

po 8. 2. 2021 v 19:35 odesílatel Matthias van de Meent napsal: > > Hi, > > With [0] we got COPY progress reporting. Before the column names of > this newly added view are effectively set in stone with the release of > pg14, I propose the following set of relatively small patches. These > are v2,

Re: proposal: schema variables

I did some testing locally. All runs smoothly, compiled without warning. Later on (once merged) it would be nice to write down a documentation page for the whole feature as a set next to documented individual commands. It took me a few moments to understand how this works. I was looking how to

Re: [PATCH] Simple progress reporting for COPY command

pá 8. 1. 2021 v 5:03 odesílatel Amit Kapila napsal: > > On Fri, Jan 8, 2021 at 8:42 AM Josef Šimánek wrote: > > > > pá 8. 1. 2021 v 3:55 odesílatel Amit Kapila > > napsal: > > > > > > > > > Can't we display the entire COPY command? I checked

Re: [PATCH] Simple progress reporting for COPY command

pá 8. 1. 2021 v 3:55 odesílatel Amit Kapila napsal: > > On Thu, Jan 7, 2021 at 7:02 PM Josef Šimánek wrote: > > > > čt 7. 1. 2021 v 14:08 odesílatel Amit Kapila > > napsal: > > > > > > On Thu, Jan 7, 2021 at 3:15 AM Tomas Vondra > > > wrote

Re: [PATCH] Simple progress reporting for COPY command

čt 7. 1. 2021 v 22:37 odesílatel Tomas Vondra napsal: > > > > On 1/7/21 7:56 PM, Josef Šimánek wrote: > > čt 7. 1. 2021 v 19:51 odesílatel Matthias van de Meent > > napsal: > >> > >> On Wed, 6 Jan 2021 at 22:45, Tomas Vondra > >> wrote:

Re: [PATCH] Simple progress reporting for COPY command

čt 7. 1. 2021 v 19:51 odesílatel Matthias van de Meent napsal: > > On Wed, 6 Jan 2021 at 22:45, Tomas Vondra > wrote: > > > > On 1/5/21 11:02 AM, Josef Šimánek wrote: > > > I'm attaching the whole patch since commitfest failed to ingest the > > > las

Re: [PATCH] Simple progress reporting for COPY command

čt 7. 1. 2021 v 16:54 odesílatel Tomas Vondra napsal: > > > > On 1/7/21 12:06 PM, Josef Šimánek wrote: > > st 6. 1. 2021 v 22:44 odesílatel Tomas Vondra > > napsal: > >> > >> On 1/5/21 11:02 AM, Josef Šimánek wrote: > >>> I'm attac

Re: [PATCH] Simple progress reporting for COPY command

čt 7. 1. 2021 v 14:08 odesílatel Amit Kapila napsal: > > On Thu, Jan 7, 2021 at 3:15 AM Tomas Vondra > wrote: > > > > On 1/5/21 11:02 AM, Josef Šimánek wrote: > > > I'm attaching the whole patch since commitfest failed to ingest the > > > last increment

Re: [PATCH] Simple progress reporting for COPY command

st 6. 1. 2021 v 22:44 odesílatel Tomas Vondra napsal: > > On 1/5/21 11:02 AM, Josef Šimánek wrote: > > I'm attaching the whole patch since commitfest failed to ingest the > > last incremental on CI. > > > > Yeah, the whole patch needs to be attached for the commitf

Re: [PATCH] Simple progress reporting for COPY command

I'm attaching the whole patch since commitfest failed to ingest the last incremental on CI. út 5. 1. 2021 v 2:32 odesílatel Josef Šimánek napsal: > > út 5. 1. 2021 v 0:46 odesílatel Tomas Vondra > napsal: > > > > Hi, > > > > I did take a quick look today, a

Re: [PATCH] Simple progress reporting for COPY command

út 5. 1. 2021 v 0:46 odesílatel Tomas Vondra napsal: > > Hi, > > I did take a quick look today, and I have a couple minor comments: Hi! Thanks for your time. > 1) The catalog sgml docs seem to mention bytes_processed twice (one of > that should be bytes_total), and line_processed (should be

Re: [PATCH] Simple progress reporting for COPY command

pá 1. 1. 2021 v 11:16 odesílatel Bharath Rupireddy napsal: > > On Fri, Jan 1, 2021 at 6:55 AM Josef Šimánek wrote: > > finally I had some time to revisit patch and all comments from > > https://www.postgresql.org/message-id/CAFp7QwqMGEi4OyyaLEK9DR0%2BE%2BoK3UtA4bEjDVCa4bNkwUY2P

[PATCH] Simple progress reporting for COPY command

Hello, finally I had some time to revisit patch and all comments from https://www.postgresql.org/message-id/CAFp7QwqMGEi4OyyaLEK9DR0%2BE%2BoK3UtA4bEjDVCa4bNkwUY2PQ%40mail.gmail.com and I have prepared simple version of COPY command progress reporting. To keep the patch small as possible, I have

Re: Github Actions (CI)

čt 3. 12. 2020 v 7:34 odesílatel Thomas Munro napsal: > > Hi hackers, > > I'm looking for more horsepower for testing commitfest entries > automatically, and today I tried out $SUBJECT. The attached is a > rudimentary first attempt, for show-and-tell. If you have a Github > account, you just

Re: Commitfest 2020-11 is closed

st 2. 12. 2020 v 23:36 odesílatel Andrew Dunstan napsal: > > > On 12/2/20 5:13 PM, Thomas Munro wrote: > > > > I'm experimenting with Github's built in CI. All other ideas welcome. > > > > I'd look very closely at gitlab. I was about to respond before with the same idea. Feel free to ping

Re: [PATCH] Initial progress reporting for COPY command

čt 17. 9. 2020 v 7:09 odesílatel Michael Paquier napsal: > > On Mon, Sep 07, 2020 at 01:13:10PM +0900, Michael Paquier wrote: > > Josef, the patch has been waiting on author for a bit more than one > > month, so could you send a rebased version please? It looks that you > > are still a bit

Re: [PATCH] Initial progress reporting for COPY command

Thanks for the info. I am waiting for review. Is there any summary of requested changes needed? Dne út 28. 7. 2020 19:00 uživatel Fujii Masao napsal: > > > On 2020/07/02 21:51, Daniel Gustafsson wrote: > >> On 2 Jul 2020, at 14:42, Josef Šimánek wrote: > >> čt 2.

Re: [PATCH] Initial progress reporting for COPY command

čt 2. 7. 2020 v 14:25 odesílatel Daniel Gustafsson napsal: > The automated patchtester for the Commitfest gets confused when there are > two > versions of the same changeset attached to the email, as it tries to apply > them > both which obviously results in an application failure. I've

Re: [PATCH] Initial progress reporting for COPY command

út 23. 6. 2020 v 13:15 odesílatel Tomas Vondra napsal: > On Tue, Jun 23, 2020 at 03:40:08PM +0530, vignesh C wrote: > >On Mon, Jun 22, 2020 at 4:28 PM Josef Šimánek > wrote: > >> > >> Thanks for the hint regarding "CopyReadLineText". I'll take a look. >

Re: [PATCH] Initial progress reporting for COPY command

po 22. 6. 2020 v 14:14 odesílatel Tomas Vondra napsal: > On Sun, Jun 21, 2020 at 01:40:34PM +0200, Josef Šimánek wrote: > >Thanks for all comments. I have updated code to support more options > >(including STDIN/STDOUT) and added some documentation. > > > >Patch is att

Re: [PATCH] Initial progress reporting for COPY command

po 22. 6. 2020 v 9:15 odesílatel vignesh C napsal: > On Sun, Jun 21, 2020 at 5:11 PM Josef Šimánek > wrote: > > > > Thanks for all comments. I have updated code to support more options > (including STDIN/STDOUT) and added some documentation. > > > > Patch

Re: [PATCH] Initial progress reporting for COPY command

po 22. 6. 2020 v 4:48 odesílatel Fujii Masao napsal: > > > On 2020/06/21 20:33, Josef Šimánek wrote: > > > > > > po 15. 6. 2020 v 6:39 odesílatel Fujii Masao < > masao.fu...@oss.nttdata.com <mailto:masao.fu...@oss.nttdata.com>> napsal: > > > >

Re: [PATCH] Initial progress reporting for COPY command

po 15. 6. 2020 v 7:34 odesílatel Bharath Rupireddy < bharath.rupireddyforpostg...@gmail.com> napsal: > > I'm using ftell to get current position in file to populate > file_bytes_processed without error handling (ftell can return -1L and also > populate errno on problems). > > > > 1. Is that a

Re: [PATCH] Initial progress reporting for COPY command

po 15. 6. 2020 v 2:18 odesílatel Michael Paquier napsal: > Hi Josef, > > On Sun, Jun 14, 2020 at 02:32:33PM +0200, Josef Šimánek wrote: > > Hello, as proposed by Pavel Stěhule and discussed on local czech > PostgreSQL > > maillist ( > > > https://groups

Re: [PATCH] Initial progress reporting for COPY command

po 15. 6. 2020 v 6:39 odesílatel Fujii Masao napsal: > > > On 2020/06/14 21:32, Josef Šimánek wrote: > > Hello, as proposed by Pavel Stěhule and discussed on local czech > PostgreSQL maillist ( > https://groups.google.com/d/msgid/postgresql-cz/CAFj8p

Re: [PATCH] Initial progress reporting for COPY command

po 15. 6. 2020 v 2:18 odesílatel Michael Paquier napsal: > Hi Josef, > > On Sun, Jun 14, 2020 at 02:32:33PM +0200, Josef Šimánek wrote: > > Hello, as proposed by Pavel Stěhule and discussed on local czech > PostgreSQL > > maillist ( > > > https://groups

[PATCH] Initial progress reporting for COPY command

Hello, as proposed by Pavel Stěhule and discussed on local czech PostgreSQL maillist ( https://groups.google.com/d/msgid/postgresql-cz/CAFj8pRCZ42CBCa1bPHr7htffSV%2BNAcgcHHG0dVqOog4bsu2LFw%40mail.gmail.com?utm_medium=email_source=footer), I have prepared an initial patch for COPY command progress

Re: Another modest proposal for docs formatting: catalog descriptions

út 2. 6. 2020 v 0:30 odesílatel Tom Lane napsal: > As of HEAD, building the PDF docs for A4 paper draws 538 "contents > ... exceed the available area" warnings. While this is a nice step > forward from where we were (v12 has more than 1500 such warnings), > we're far from done fixing that

Re: [PATCH] Improve documentation of REINDEX options

út 17. 12. 2019 v 6:36 odesílatel Michael Paquier napsal: > On Fri, Dec 13, 2019 at 10:28:33AM +0100, Josef Šimánek wrote: > > I have prepared patch to improve documentation for REINDEX. It > > should be more inline with another documentation pages. > > > > You

Re: [PATCH] Improve documentation of REINDEX options

út 17. 12. 2019 v 6:36 odesílatel Michael Paquier napsal: > On Fri, Dec 13, 2019 at 10:28:33AM +0100, Josef Šimánek wrote: > > I have prepared patch to improve documentation for REINDEX. It > > should be more inline with another documentation pages. > > > > You

[PATCH] Improve documentation of REINDEX options

Hello! According to discussion at pgsql-general ( https://www.postgresql.org/message-id/flat/CAFp7QwqFYcHiARfT91rOQj%3DmFT0MWBE%2BkxEmjfQh3QmRN1UBiw%40mail.gmail.com#05b75be4fd11c0e6216f0b329c808f72) I have prepared patch to improve documentation for REINDEX. It should be more inline with another

Re: [PATCH] Include triggers in EXPLAIN

Hello Tom. Thanks for quick response. As I was testing this feature it shows all "possible" triggers to be executed running given query. The benefit of having this information in EXPLAIN as well is you do not need to execute the query (as EXPLAIN ANALYZE does). My usecase is to take a look at

[PATCH] Include triggers in EXPLAIN

PS: This is my first try to contribute to postgresql codebase. The quality of patch is probably not the best, but I will be more than happy to do any requested change if needed. Regards, Josef Šimánek From 18578e3d07aa159631e0903abae496a6482fa279 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Josef=20=C5