threads listlengths 1 2.99k |
|---|
[
{
"msg_contents": "\n\n\n> On Jun 14, 2022, at 19:06, Thomas Munro <thomas.munro@gmail.com> wrote:\n> One difference would be the effect if ICU ever ships a minor library\n> version update that changes the reported collversion.\n\nIf I’m reading it correctly, ICU would not change collation in major versions, ... |
[
{
"msg_contents": "Dear Postgres,\n\nRecently I work on grouping sets and I find the last param numGroups of create_groupingsets_path is not used.\nIn create_groupingsets_path we use rollup->numGroups to do cost_agg. So I remove the param numGroups for\ncreate_groupingsets_path.\n\nI generate a diff.patch, whic... |
[
{
"msg_contents": "Hi all!\n\nThe motivation behind this is that incrementally building up a GiST \nindex for certain input data can create a terrible tree structure.\nFurthermore, exclusion constraints are commonly implemented using GiST \nindices and for that use case, data is mostly orderable.\n\nBy sorting ... |
[
{
"msg_contents": "Adding a plan_id to pg_stat_activity allows users\r\nto determine if a plan for a particular statement\r\nhas changed and if the new plan is performing better\r\nor worse for a particular statement.\r\n\r\nThere are several ways the plan_id in pg_stat_activity\r\ncan be used:\r\n\r\n1. In ext... |
[
{
"msg_contents": "Hackers,\n\nWhile developing various Table Access Methods, I have wanted a callback for determining if CLUSTER (and VACUUM FULL) should be run against a table backed by a given TAM. The current API contains a callback for doing the guts of the cluster, but by that time, it's a bit too late t... |
[
{
"msg_contents": "Hackers,\n\nI have extended the grammar to allow \"USING NOT method [, ...]\" to exclude one or more TAMs in a CREATE TABLE statement. This may sound like a weird thing to do, but it is surprisingly useful when developing new Table Access Methods, particularly when you are developing two or ... |
[
{
"msg_contents": "FYI, I happened to notice in the PG docs there are a few integer\nconfiguration parameters that describe themselves as type \"(int)\"\ninstead of \"(integer)\".\n\nIt looked like a small mistake to me; there are only 3 of (int),\nversus 148 of (integer).\n\n~~~\n\ndoc\\src\\sgml\\auth-delay.s... |
[
{
"msg_contents": "Dear PostgreSQL Developers,\n\nI'm currently working on a GiST extension (a new index structure) for PostgreSQL\nand I want to make it as customizable as I can. To achieve my goal I'm trying to take\nadvantage of the options GiST support function to provide extra parameters to the\noperator c... |
[
{
"msg_contents": "Hi,\nI'm reading the docs (I'm trying to figure out some replication\nthings) and I was wondering why the file references [1] don't match\nthe file names.\n\nMost of the inconsistent items are for `obsolete-*` where the filename\nis actually `appendix-obsolete-*`. But, oddly, afaict, they wer... |
[
{
"msg_contents": "libpq contains a lot of\n\n if (foo)\n free(foo);\n\ncalls, where the \"if\" part is unnecessary. This is of course pretty \nharmless, but some functions like scram_free() and freePGconn() have \nbecome so bulky that it becomes annoying. So while I was doing some \nwork in that ... |
[
{
"msg_contents": "While browsing through some of the clock-sweep code I noticed that the \nonly place StrategyNotifyBgWriter() is called now is in \nBackgroundWriterMain()[1]. Presumably this isn't what's desired. If \nnothing else, it means the function's description comment is wrong, as \nare comments in Bac... |
[
{
"msg_contents": "Hi,\n\nMark Callaghan reported a regression in 15, in the post linked here (with\ncomments in the twitter thread, hence linked here)\nhttps://twitter.com/MarkCallaghanDB/status/1537475430227161098\n\nA differential flame graph shows increased time spent doing memory\nallocations, below ExecIn... |
[
{
"msg_contents": "Hi hackers,\n\n I thought it would be nice to have an configuration example of the pg_prewarm extension.\n Therefore, I have written an example of a basic configuration.\n\n ---\n Regards,\n DongWook Lee",
"msg_date": "Sat, 18 Jun 2022 17:55:41 +0900",
"msg_from": "Dong Wook Lee <sh95... |
[
{
"msg_contents": "Extension version strings need to be quoted. Either double or single\nquotes will work. In released psql clients, tab completion offers double\nquoted suggestions:\n\nalter extension pg_trgm update TO <tab><tab>\n\"1.3\" \"1.4\" \"1.5\" \"1.6\"\n\nBut commit 02b8048ba5 broke that, it now... |
[
{
"msg_contents": "Hi hackers,\n\nIn several conversations I had recently with colleagues it was pointed\nout that it would be great if PostgreSQL supported COPY to/from\nParquet and other formats. I've found a corresponding discussion [1]\non pgsql-general@. The consensus reached back in 2018 seems to be that\... |
[
{
"msg_contents": "Hi all,\n\nIf there's not already a manager for the upcoming (July 2022)\ncommitfest, I'd like to volunteer. (And if there is, I'm happy to\nassist and start learning the ropes, if that would be helpful.)\n\n--Jacob\n\n\n",
"msg_date": "Mon, 20 Jun 2022 12:29:57 -0500",
"msg_from": "J... |
[
{
"msg_contents": "Hi hackers!\n\nRecently we faced a problem with one of our production clusters. We use a\ncascade replication setup in this cluster, that is: master, standby (r1),\nand cascade standby (r2). From time to time, the replication lag on r1 used\nto grow, while on r2 it did not. Analysys showed th... |
[
{
"msg_contents": "I suggest that we add the gcc (also clang) option -ftabstop=4.\n\nThis has two effects: First, it produces more accurate column numbers \nin compiler errors and correctly indents the code excerpts that the \ncompiler shows with those. Second, it enables the compiler's detection \nof confusi... |
[
{
"msg_contents": "Hi,\r\n\r\nThe RMT[1] with the release team has set a date of June 30, 2022 for the \r\nPostgreSQL 15 Beta 2 release. We encourage you to try to close as many \r\nopen items[2] prior to the release.\r\n\r\nIf you are working on patches for Beta 2, please be sure that they are \r\ncommitted no... |
[
{
"msg_contents": "Hi,\n\nProblem: Today when a data page is corrupted in the primary postgres with\nphysical replication (sync or async standbys), there seems to be no way to\nrepair it easily and we rely on PITR to recreate the postgres server or\ndrop the corrupted table (of course this is not an option for ... |
[
{
"msg_contents": "Hi hackers,\n\nI think there's a missing reference to pgstat_replslot.c in pgstat.c.\n\nAttached a tiny patch to fix it.\n\nRegards,\nBertrand",
"msg_date": "Wed, 22 Jun 2022 08:29:03 +0200",
"msg_from": "\"Drouvot, Bertrand\" <bdrouvot@amazon.com>",
"msg_from_op": true,
"msg_... |
[
{
"msg_contents": "This possible change was alluded to in the meson thread at [0].\n\nThe proposal is to move the list of available languages from nls.mk into \na separate file called po/LINGUAS. Advantages:\n\n- It keeps the parts notionally managed by programmers (nls.mk)\n separate from the parts notional... |
[
{
"msg_contents": "macOS has traditionally used extension .dylib for shared libraries (used \nat build time) and .so for dynamically loaded modules (used by \ndlopen()). This complicates the build system a bit. Also, Meson uses \n.dylib for both, so it would be worth unifying this in order to be able \nto get... |
[
{
"msg_contents": "Hi hackers,\n\nThe SYSTEM_USER is a sql reserved word as mentioned in [1] and is \ncurrently not implemented.\n\nPlease find attached a patch proposal to make use of the SYSTEM_USER so \nthat it returns the authenticated identity (if any) (aka authn_id in the \nPort struct).\n\nIndeed in some... |
[
{
"msg_contents": "ATRewriteTable() calls table_tuple_insert() with a bistate, to avoid clobbering\nand polluting the buffers.\n\nBut heap_insert() then calls \nheap_prepare_insert() >\nheap_toast_insert_or_update >\ntoast_tuple_externalize >\ntoast_save_datum >\nheap_insert(toastrel, toasttup, mycid, options, ... |
[
{
"msg_contents": "Hi all,\r\n\r\nPostgreSQL currently maintains several data structures in the SLRU\r\ncache. The SLRU cache has scaling and sizing challenges because of it’s\r\nsimple implementation. The goal is to move these caches to the common\r\nbuffer cache to benefit from the stronger capabilities of th... |
[
{
"msg_contents": "Hi all,\n(Thomas and Andres in CC.)\n\nAndres has complained a couple of days ago about the quantity of logs\nthat can be fed into the TAP tests running pg_regress:\nhttps://www.postgresql.org/message-id/20220603195318.qk4voicqfdhlsnoh@alap3.anarazel.de\n\nThis concerns the TAP tests of pg_up... |
[
{
"msg_contents": "I have been trying to find active interest for volunteer development of a GPL license style PostgreSQL extension (or default PostgreSQL additions), complete and available, on Sourceforge, PGXN and the public internet, that will support the following:\n\nHigh Precision Arithmetic and Elementar... |
[
{
"msg_contents": "PSA trivial patch fixing a harmless #define typo.\n\n------\nKind Regards,\nPeter Smith.\nFujitsu Australia",
"msg_date": "Thu, 23 Jun 2022 17:35:37 +1000",
"msg_from": "Peter Smith <smithpb2250@gmail.com>",
"msg_from_op": true,
"msg_subject": "Fix typo in pg_publication.c"
... |
[
{
"msg_contents": "Hackers,\n\nSome PostgreSQL extensions need to sort their pieces of data. Then it\nworth to re-use our tuplesort. But despite our tuplesort having\nextensibility, it's hidden inside tuplesort.c. There are at least a\ncouple of examples of how extensions deal with that.\n\n1. RUM table access ... |
[
{
"msg_contents": "Hi,\n\nI noticed BF member wrasse failed in 028_row_filter.pl.\n\n# Failed test 'check publish_via_partition_root behavior'\n# at t/028_row_filter.pl line 669.\n# got: ''\n# expected: '1|100\n# ...\n\nLog:\n2022-06-23 11:27:42.387 CEST [20589:3] 028_row_filter.pl... |
[
{
"msg_contents": "Hi hackers,\nAlong with major TOAST improvement with Pluggable TOAST we see the really\nimportant smaller one - moving compression functionality when dealing with\noversized Tuples into Toast, because Toast is meant to deal with how\noversized Tuple is stored and it is logical to make it resp... |
[
{
"msg_contents": "Some places in walsender.c and basebackup_copy.c open-code the sending \nof RowDescription and DataRow protocol messages. But there are already \nmore compact and robust solutions available for this, using \nDestRemoteSimple and associated machinery, already in use in walsender.c.\n\nThe att... |
[
{
"msg_contents": "Moved from the pgsql-bugs mailing list [1].\n\nOn 6/23/22 07:03, Masahiko Sawada wrote:\n > Hi,\n >\n > On Sat, Jun 4, 2022 at 4:03 AM Andrey Lepikhov\n > <a.lepikhov@postgrespro.ru> wrote:\n >>\n >> According to subj you can try to create many tables (induced by the case\n >> of partitioned ... |
[
{
"msg_contents": "\n<sigh>\n\nJust a note/reminder that \"seawasp\" has been unhappy for some days now \nbecause of yet another change in the unstable API provided by LLVM:\n\nhttps://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=seawasp&dt=2022-06-23%2023%3A18%3A17\n\n llvmjit.c:1115:50: error: use of unde... |
[
{
"msg_contents": "When parsing JSON strings need to be converted from the JSON string\nformat to a c-style string. A simple copy of the buffer does not suffice\nbecause of the various escape sequences that that JSON supports. Because\nof this our JSON parser wrote characters into the c-style string buffer\none... |
[
{
"msg_contents": "Hi,\n\nI'm trying to have a setup where there is a primary, standby and\npg_receivewal (which acts as a server that maintains the entire WAL).\nQuorum is any one of standby and pg_receivewal. In case of primary crash,\nwhen I promote standby (timeline switch from 5 to 6) and restart\npg_recei... |
[
{
"msg_contents": "Hi,\n\n\nI have a made a small deductive database on top of PostgreSQL for educational/research purposes. In this setting, due to certain VIEW-constructions, queries often end up being self-joins on primary keys, e.g.:\n\n\nSELECT t1.id, t2.val\n\nFROM t AS t1 JOIN t AS t2 USING (id);\n\n\nwh... |
[
{
"msg_contents": "Hi,\n\nI noticed that in many places we check or assert the OIDs of our\nbuilt-in AMs. E.g. in planning, we will only do row compares in\nindexes that have BTREE_AM_OID, and we can only sort tuples for\nbtamhandler -based index ams if their oid is the BTREE_AM_OID. That\nseems like an artific... |
[
{
"msg_contents": "Hi,\nLooking at the patch,\n\n+ if (copyable_characters_length)\n+ {\n+ /* flush copyable characters */\n+ appendBinaryStringInfo(\n+ lex->strval,\n+ s - copyable_characte... |
[
{
"msg_contents": "Commit 64919aaab made pull_up_simple_subquery set rte->subquery = NULL\nafter doing the deed, so that we don't waste cycles copying a\nnow-useless subquery tree around. I discovered today while\nworking on another patch that if you invoke query_tree_mutator\nor range_table_mutator on the who... |
[
{
"msg_contents": "Hi Pgsql-Hackers\n\nAs part of ongoing work on PostgreSQL security hardening we have\nadded a capability to disable all file system access (COPY TO/FROM\n[PROGRAM] <filename>, pg_*file*() functions, lo_*() functions\naccessing files, etc) in a way that can not be re-enabled without\nalready ... |
[
{
"msg_contents": "Now that I've gotten your attention..\n\nI expect pg_upgrade to fail if I run it twice in a row.\n\nIt would be reasonable if it were to fail during the \"--check\" phase,\nmaybe by failing like this:\n| New cluster database \"...\" is not empty: found relation \"...\"\n\nBut that fails to ha... |
[
{
"msg_contents": "JSON/SQL jsonpath\n\nFor example, a jsonpath string with deliberate typo 'like_regexp' \n(instead of 'like_regex'):\n\nselect js\nfrom (values (jsonb '{}')) as f(js)\nwhere js @? '$ ? (@ like_regexp \"^xxx\")';\n\nERROR: syntax error, unexpected IDENT_P at or near \" \" of jsonpath input\nLI... |
[
{
"msg_contents": "Hello Hackers,\n\nWhile working on one of my blogs on the B-Tree indexes\n<https://www.percona.com/blog/postgresql-14-b-tree-index-reduced-bloat-with-bottom-up-deletion/>,\nI needed to look at a range of B-Tree page statistics. So the goto solution\nwas to use pageinspect. However, reviewing ... |
[
{
"msg_contents": "Hi,\n\nToday, postgres doesn't distinguish the log messages that it emits to\nserver logs via ereport/elog mechanism, based on security information or\nPII (Personally Identifiable Information) or other sensitive information\n[1]. In production environments, these log messages would be captur... |
[
{
"msg_contents": "This was discussed previously in [1], and there seemed to be general\nconsensus in favour of it, but no new patch emerged.\n\nAttached is a patch that takes the approach of not generating an alias\nat all, which seems to be neater and simpler, and less code than\ntrying to generate a unique a... |
[
{
"msg_contents": "Hi all,\n\nJust a reminder that the July 2022 commitfest will begin this coming\nFriday, July 1. I'll send out reminders this week to get your patches\nregistered/rebased, and I'll be updating stale statuses in the CF app.\n\nThanks,\n--Jacob\n\n\n",
"msg_date": "Mon, 27 Jun 2022 08:33:19... |
[
{
"msg_contents": "Hey,\r\n\r\nIf I understand correctly, when a Sequential Scan takes place, the ExecScan function (located in executor/execScan.c) does not retrieve all attributes per tuple in the TupleTableSlot and only retrieves the necessary attribute. So for example, let’s imagine we have a table t1 with ... |
[
{
"msg_contents": "Hi all,\n(Andrew in CC.)\n\nWhen running installcheck multiple times under src/test/modules/, we\nare getting two failures as of test_pg_dump and test_oat_tests,\nbecause these keep around some roles created by the tests.\n\nKeeping around a role for test_pg_dump has been discussed already,\n... |
[
{
"msg_contents": "Hi all,\n\nWhile browsing through the recent changes with the base backup APIs, I\nhave noticed that a couple of comments did not get the renaming of the\nSQL functions to pg_backup_start/stop, as of the attached.\n\nThat's not a big deal, but let's be right.\n\nThanks,\n--\nMichael",
"ms... |
[
{
"msg_contents": "(Starting a new thread)\n\nOn Sun, Jun 26, 2022 at 10:48:24AM +0800, Julien Rouhaud wrote:\n> On Thu, Jun 23, 2022 at 10:19:44AM -0400, Robert Haas wrote:\n> > On Thu, Jun 23, 2022 at 6:13 AM Julien Rouhaud <rjuju123@gmail.com> wrote:\n> >\n> > > And should record_in / record_out use the logi... |
[
{
"msg_contents": "I have been interested in a query that returns a batch of results filtered\nby a subset of the first column of an index and ordered by the second.\n\nI created a simple (hopefully) reproducible example of the issue, the two\nqueries describe the same data but have very different costs (explai... |
[
{
"msg_contents": "I don´t know how to create a patch, maybe someday, but for now I´m just\nsending this little problem if somebody can solve it.\n\nIn a multi schema environment where several tables has same structure is a\nlittle bit hard to know which one already has that primary key.\n\nOn log I see now on ... |
[
{
"msg_contents": "Patch attached. Some kinds of emit log hooks might find it useful to\nalso compute the log_line_prefix.\n\nRegards,\n\tJeff Davis",
"msg_date": "Tue, 28 Jun 2022 11:52:56 -0700",
"msg_from": "Jeff Davis <pgsql@j-davis.com>",
"msg_from_op": true,
"msg_subject": "Export log_line... |
[
{
"msg_contents": "Patch attached.\n\nHelpful for debugging complex extension script problems.",
"msg_date": "Tue, 28 Jun 2022 12:10:26 -0700",
"msg_from": "Jeff Davis <pgsql@j-davis.com>",
"msg_from_op": true,
"msg_subject": "Emit extra debug message when executing extension script."
},
{
... |
[
{
"msg_contents": "Hi,\n\nI found a comparaison bug when using the PostgreSQL::Version module. See:\n\n $ perl -I. -MPostgreSQL::Version -le '\n my $v = PostgreSQL::Version->new(\"9.6\");\n \n print \"not 9.6 > 9.0\" unless $v > 9.0;\n print \"not 9.6 < 9.0\" unless $v < 9.0;\n print \"9.6 <= 9.... |
[
{
"msg_contents": "Here's a patch to clarify the BRIN indexes documentation, particularly with\nregards\nto autosummarize, vacuum and autovacuum. It basically breaks down a big\nblob of a\nparagraph into multiple paragraphs for clarity, plus explicitly tells how\nsummarization\nhappens manually or automatically... |
[
{
"msg_contents": "Hi,\r\n\r\nAttached is a draft of the release announcement for PostgreSQL 15 Beta \r\n2. Please provide feedback on technical accuracy and if there are \r\nglaring omissions.\r\n\r\nPlease provide any feedback prior to 2022-06-22 0:00 AoE.\r\n\r\nThanks,\r\n\r\nJonathan",
"msg_date": "Tue... |
[
{
"msg_contents": "Hackers,\n\nI noticed while doing some memory context related work that since we\nnow use generation.c memory contexts for tuplesorts (40af10b57) that\ntuplesort_putindextuplevalues() causes memory \"leaks\" in the\ngeneration context due to index_form_tuple() being called while we're\nswitch... |
[
{
"msg_contents": "Over on [1] I noticed that the user had set force_parallel_mode to\n\"on\" in the hope that would trick the planner into making their query\nrun more quickly. Of course, that's not what they want since that GUC\nis only there to inject some parallel nodes into the plan in order to\nverify th... |
[
{
"msg_contents": "Hi hackers,\nI wrote a test for pg_prewarm extension. and I wrote it with the aim of improving test coverage, and feedback is always welcome.\n\n---\nRegards\nDongWook Lee",
"msg_date": "Wed, 29 Jun 2022 14:38:12 +0900",
"msg_from": "Dong Wook Lee <sh95119@gmail.com>",
"msg_from_o... |
[
{
"msg_contents": "Hi Hackers,\nI just wrote test about pg_rowlocks extension.\nI added sql and spec test for locking state.\n\n---\nRegards\nDongWook Lee",
"msg_date": "Wed, 29 Jun 2022 14:53:26 +0900",
"msg_from": "Dong Wook Lee <sh95119@gmail.com>",
"msg_from_op": true,
"msg_subject": "add te... |
[
{
"msg_contents": "Hi,\n\nchipmunk (an armv6l-powered original Raspberry Pi model 1?) has failed\nin a couple of weird ways recently on 14 and master.\n\nOn 14 I see what appears to be a corrupted log file name:\n\nhttps://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=chipmunk&dt=2022-06-16%2006%3A48%3A07\n\n... |
[
{
"msg_contents": "Hello,\n\nDuring checking regression tests of TRUNCATE on foreign\ntables for other patch [1], I found that there is no test\nfor foreign tables that don't support TRUNCATE. \n\nWhen a foreign table has handler but doesn't support TRUNCATE,\nan error \"cannot truncate foreign table xxx\" occu... |
[
{
"msg_contents": "Hi,\n\nI found that the assertion failure and the segmentation fault could\nhappen by running pg_backup_start(), pg_backup_stop() and BASE_BACKUP\nreplication command, in v15 or before.\n\nHere is the procedure to reproduce the assertion failure.\n\n1. Connect to the server as the REPLICATION... |
[
{
"msg_contents": "Hi,\n\nI found that there is no index item for MERGE command, in the docs.\nAttached is the patch that adds the indexterm for MERGE to merge.sgml.\n\nRegards,\n\n-- \nFujii Masao\nAdvanced Computing Technology Center\nResearch and Development Headquarters\nNTT DATA CORPORATION",
"msg_date... |
[
{
"msg_contents": "Hi hackers,\n\nWhile commit 960869da08 added some information about connections that \nhave been successfully authenticated, there is no metrics for \nconnections that have not (or did not reached the authentication stage).\n\nAdding metrics about failed connections attempts could also help, ... |
[
{
"msg_contents": "Hello,\n\nI propose supporting TRUNCATE triggers on foreign tables\nbecause some FDW now supports TRUNCATE. I think such triggers\nare useful for audit logging or for preventing undesired\ntruncate.\n\nPatch attached.\n\nRegards,\nYugo Nagata\n\n-- \nYugo NAGATA <nagata@sraoss.co.jp>",
"m... |
[
{
"msg_contents": "Hi,\n\nI was just looking at the list of predefined roles that we have, and\npg_checkpointer is conspicuously not like the others:\n\nrhaas=# select rolname from pg_authid where oid!=10;\n rolname\n---------------------------\n pg_database_owner\n pg_read_all_data\n pg_write_all_data... |
[
{
"msg_contents": "Hi,\n\nI was dismayed to learn that VACUUM VERBOSE on a table no longer tells\nyou anything about whether any pages were skipped due to pins. Now the\nobvious explanation for that is that we no longer skip pages entirely\njust because we find that they are pinned. But I think failing to\nfull... |
[
{
"msg_contents": "Hi Hackers,\n\n\n\nI have been using pg_rewind in production for 2 years. One of the things that I noticed in pg_rewind is if it doesn't know what to do with a file \"it copies\". I understand it's the more safer option. After all, the alternative, pg_basebackup copies all the files from sour... |
[
{
"msg_contents": "Hi,\nGiven a query:\nSELECT * FROM t1, t2 WHERE t1.r << t2.r\nwhere t1.r, t2.r are of range type,\ncurrently PostgreSQL will estimate a constant selectivity for the << predicate,\nwhich is equal to 0.005, not utilizing the statistics that the optimizer\ncollects for range attributes.\n\nWe ha... |
[
{
"msg_contents": "Hello all,\n\nI'll be opening the July Commitfest in approximately 24 hours, so you\nhave a little more time to register any patchsets you'd like the\ncommunity to review. And remember to keep your review karma positive:\nover the next month, try to review other patches of equivalent\ncomplex... |
[
{
"msg_contents": "Hello!\n\nThis patch adds a `--tableam=TABLEAM` option to the pgbench command line\nwhich allows the user to specify which table am is used to create tables\ninitialized with `-i`.\n\nThis change was originally authored by Alexander Korotkov, I have updated\nit and added a test to the pgbench... |
[
{
"msg_contents": "Hello hackers,\n\nCurrently the red-black tree implementation only has an equality search.\nOther extensions might need other comparison searches, like less-or-equal\nor greater-or-equal. For example OrioleDB defines a greater-or-equal search\non its postgres fork:\n\nhttps://github.com/oriol... |
[
{
"msg_contents": "Hackers,\n\nwe have supported custom nodes for while. Custom slots are a bit more\n\"recent\" feature. Since we now support custom slots, which could\nhandle custom tuple format, why not allow custom nodes to use them?\n\nFor instance, a custom table access method can have its own tuple\nform... |
[
{
"msg_contents": "Hi,\n\nThere are instances where pgstat_setup_memcxt() and\npgstat_prep_pending_entry() are invoked before the CacheMemoryContext\nhas been created. This results in PgStat* contexts being created\nwithout a parent context. Most easily reproduced/seen in autovacuum\nworker via pgstat_setup_m... |
[
{
"msg_contents": "Hi,\n\nI would like to submit patch for column wait_event of view \npg_stat_activity. Please find it attached.\n\nThe view pg_stat_activity provides snapshot of actual backends' state \nwith following columns:\n - wait_event contains event name for which backend is waiting for;\n - state ... |
[
{
"msg_contents": "Hi,\n\nI had proposed $subject for some RI trigger functions in the last dev\ncycle [1]. Briefly, the proposal was to stop using an SQL query\n(using the SPI interface) for RI checks that could be done by directly\nscanning the primary/unique key index of the referenced table, which\nmust al... |
[
{
"msg_contents": "Hackers,\n\nWhen working in the read committed transaction isolation mode\n(default), we have the following sequence of actions when\ntuple_update() or tuple_delete() find concurrently updated tuple.\n\n1. tuple_update()/tuple_delete() returns TM_Updated\n2. tuple_lock()\n3. Re-evaluate plan ... |
[
{
"msg_contents": "Is it time to drop support for the oldest release ?\nAs in cf0cab868 30e7c175b e469f0aaf c03b7f526 492046fa9\n\nIf we also did the same thing next year, it'd be possible to use ::regnamespace\nwith impunity...\n\n\n",
"msg_date": "Fri, 1 Jul 2022 08:23:40 -0500",
"msg_from": "Just... |
[
{
"msg_contents": "Hello!\n\nIt's been July everywhere on Earth for a few hours, so the July\ncommitfest is now in progress:\n\n https://commitfest.postgresql.org/38/\n\nNew patches may be registered for the next commitfest in September.\nPick some patches to review and have fun!\n\nHappy hacking,\n--Jacob\n... |
[
{
"msg_contents": "Nicola Contu reported two years ago to pgsql-general[1] that they were\nhaving sporadic query failures, because EINTR is reported on some system\ncall. I have been told that the problem persists, though it is very\ninfrequent. I propose the attached patch. Kyotaro proposed a slightly\ndiff... |
[
{
"msg_contents": "[ Before settling into commitfest mode, I wanted to put out a snapshot\nof what I've been working on for the past few weeks. This is not\nanywhere near committable, but I think people might be interested\nin looking at it now anyway. ]\n\nWe've had many discussions (eg [1][2]) about the need... |
[
{
"msg_contents": "Hi hackers,\n\nThe unparenthesized syntax for VACUUM has been marked deprecated since v9.1\n(ad44d50). Should it be removed in v16? If not, should we start emitting\nWARNINGs when it is used?\n\n-- \nNathan Bossart\nAmazon Web Services: https://aws.amazon.com\n\n\n",
"msg_date": "Fri, 1... |
[
{
"msg_contents": "I noticed this during beta1, but dismissed the issue when it wasn't easily\nreproducible. Now, I saw the same problem while upgrading from beta1 to beta2,\nso couldn't dismiss it. It turns out that LOs are lost if VACUUM FULL was run.\n\n| /usr/pgsql-15b1/bin/initdb --no-sync -D pg15b1.dat ... |
[
{
"msg_contents": "Hi,\n\n(sorry for sending this twice to you Noah, forgot -hackers the first time\nround)\n\nWe've had a bunch of changes to manually deal with our alignment code not\nunderstanding AIX alignment.\n\ncommit f3b421da5f4addc95812b9db05a24972b8fd9739\nAuthor: Peter Eisentraut <peter_e@gmx.net>\nD... |
[
{
"msg_contents": "Buildfarm member thorntail has yet to pass the pg_upgrade test\nin the REL_15_STABLE branch. It looks like the problem reduces to\nan overlength pathname:\n\n2022-07-04 00:27:03.404 MSK [2212393:2] LOG: Unix-domain socket path \"/home/nm/farm/sparc64_deb10_gcc_64_ubsan/REL_15_STABLE/pgsql.b... |
[
{
"msg_contents": "Change timeline field of IDENTIFY_SYSTEM to int8\n\nIt was int4, but in the other replication commands, timelines are\nreturned as int8.\n\nReviewed-by: Nathan Bossart <nathandbossart@gmail.com>\nDiscussion: https://www.postgresql.org/message-id/flat/7e4fdbdc-699c-4cd0-115d-fb78a957fc22@enter... |
[
{
"msg_contents": "Hi.\n\nBy convention, the tab-complete logical replication subscription\nparameters are listed in the COMPLETE_WITH lists in alphabetical\norder, but when the \"disable_on_error\" parameter was added this was\nnot done.\n\nThis patch just tidies that up; there is no functional change.\n\nPSA\... |
[
{
"msg_contents": "Hi hackers,\n\nI think having number of index scans of the last vacuum in \npg_stat_all_tables can be helpful. This value shows how efficiently \nvacuums have performed and can be an indicator to increase \nmaintenance_work_mem.\n\nIt was proposed previously[1], but it was not accepted due to... |
[
{
"msg_contents": "Hi team, \n\n\n We are using a script to install Postgres from source, the script works fine in ubuntu and Mac(intel) but mostly fails(works sometimes) in Mac M1. \n\n\nConfigure and make world works fine. But fails during make install-world.\n\n\n/Applications/Xcode.app/Contents/Develop... |
[
{
"msg_contents": "In reviewing Peter's patch to auto-generate the backend/nodes\nsupport files, I compared what the patch's script produces to\nwhat is in the code now. I found several discrepancies in the\nrecently-added parse node types for JSON functions, and as far\nas I can see every one of those discrep... |
[
{
"msg_contents": "Hi all,\n\nWhile looking at the buildfarm logs, I have noticed the following\nthing:\nhttps://buildfarm.postgresql.org/cgi-bin/show_stage_log.pl?nm=morepork&dt=2022-07-05%2002%3A45%3A32&stg=recovery-check\n\npostgres:/usr/local/lib/libldap_r.so.13.2:\n/usr/local/lib/libldap.so.13.2 : WARNING:... |
[
{
"msg_contents": "I found that provolatile attribute of to_timestamp in pg_proc is\nwrong:\n\ntest=# select provolatile, proargtypes from pg_proc where proname = 'to_timestamp' and proargtypes[0] = 701;\n provolatile | proargtypes \n-------------+-------------\n i | 701\n(1 row)\n\n'i' (immutable) is... |
[
{
"msg_contents": "Hello hackers,\n \nIt seems useful to have [OR REPLACE] option in CREATE OPERATOR statement, as in CREATE FUNCTION. This option may be good for writing extension update scripts, to avoid errors with re-creating the same operator.\n \nBecause of cached query plans, only RESTRICT and JOIN optio... |
[
{
"msg_contents": "Hi hackers,\n\nI created a patch to reuse tablesync workers and their replication slots\nfor more tables that are not synced yet. So that overhead of creating and\ndropping workers/replication slots can be reduced.\n\nCurrent version of logical replication has two steps: tablesync and apply.\... |
[
{
"msg_contents": "Hi,\n\nThere's a number of symbols that are exported by libpq that are also in\nbinaries (mostly via pgport). That strikes me as not great, because the\nbehaviour in those cases isn't particularly well defined / OS dependent /\nlinker option dependent.\n\nHow about renaming those functions, t... |
[
{
"msg_contents": "The following bug has been logged on the website:\n\nBug reference: 17540\nLogged by: William Duclot\nEmail address: william.duclot@gmail.com\nPostgreSQL version: 14.4\nOperating system: GNU/Linux (Red Hat 8.5.0)\nDescription: \n\nMy application uses prepared state... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.