threads listlengths 1 2.99k |
|---|
[
{
"msg_contents": " From 73dbe66c0ed68ae588223639a2ba93f6a727b704 Mon Sep 17 00:00:00 2001\nFrom: Samuel Marks <807580+SamuelMarks@users.noreply.github.com>\nDate: Fri, 23 Aug 2024 16:03:41 -0500\nSubject: [PATCH] [src/include/pg_config_manual.h] Guard `CLOBBER_FREED_MEMORY`\n & `MEMORY_CONTEXT_CHECKING`\n\n---... |
[
{
"msg_contents": "Here is a patch to replace a getpwuid() call in the backend, for \nthread-safety.\n\nThis is AFAICT the only call in the getpw*() family that needs to be \ndealt with.\n\n(There is also a getgrnam() call, but that is called very early in the \npostmaster, before multiprocessing, so we can lea... |
[
{
"msg_contents": "The list of acknowledgments for the PG17 release notes has been \ncommitted. You can see it here:\n\nhttps://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=doc/src/sgml/release-17.sgml;h=08a479807ca2933668dede22e4e6f464b937ee45;hb=refs/heads/REL_17_STABLE#l3229\n\nAs usual, please chec... |
[
{
"msg_contents": "Hi,\n\nusing `PostgreSQL 16.2 (Debian 16.2-1.pgdg120+2) on x86_64-pc-linux-gnu, \ncompiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit`, I've observed the \nfollowing behavior:\n\n– keep in mind that this example is as simplified as possible, the \noriginal query involves foreign tables, and the... |
[
{
"msg_contents": "Hi all,\n\nWhile working more on the cumulative pgstats and its interactions with\npg_stat_statements, one thing that I have been annoyed with is that\nthe dshash key for variable-numbered stats uses a pair of (Oid dboid,\nOid objoid), mostly to stick with the fact that most of the stats are\... |
[
{
"msg_contents": "Hi all,\n(Nathan in CC regarding c8b06bb969bf)\n\nWhile rebasing my patch set for sequence AMs, I've looked at what has\nbeen done with c8b06bb969bf and pg_sequence_read_tuple() because I can\nreuse it in the sequence AM patch to grab the last value of a sequence\nand if it has been called (t... |
[
{
"msg_contents": "hello,all,\nI am a newcomer who recently joined the PostgreSQL community. I logged into the community using my GitHub account and wanted to start familiarizing myself with community work by reviewing patches. However, I am currently facing an issue. When I log into commitfest.postgresql.org, ... |
[
{
"msg_contents": "Hi\n\nI checked our implementation of xmlserialize, and it looks like there are\nfew issues.\n\n1. It doesn't conform to SQL/XML - there is some overlap with the proposed\nCANONICAL flag, but not full.\n\n2. There is significantly different behaviour of NO INDENT on Oracle and\nother db, that... |
[
{
"msg_contents": "This patch allows using text position search functions with \nnondeterministic collations. These functions are\n\n- position, strpos\n- replace\n- split_part\n- string_to_array\n- string_to_table\n\nwhich all use common internal infrastructure.\n\n(This complements the patch \"Support LIKE w... |
[
{
"msg_contents": "I'm reposting this patch in a separate thread so I can make a separate \ncommitfest entry for it. The previous discussion is mixed in with [0].\n\nThe purpose of this patch is to allow using pg_upgrade between clusters \nthat have different checksum settings. When upgrading between instance... |
[
{
"msg_contents": "Hi,\n\nWhen I read the following documentation related to the \"synchronized_standby_slots\", I misunderstood that data loss would not occur in the case of synchronous physical replication. However, this is incorrect (see reproduce.txt).\n\n> Note that in the case of asynchronous replication,... |
[
{
"msg_contents": "Hi PostgreSQL Community,\nI have encountered an issue when attempting to use pgstattuple extension\nwith sequences. When executing the following command:\n\nSELECT * FROM pgstattuple('serial');\nERROR: only heap AM is supported\n\nThis behaviour is observed in PostgreSQL versions post v11 [1... |
[
{
"msg_contents": "Hi!\n\nThis is my first time contribution to the PostgreSQL, so I’m not really\nfamiliar with the whole process. The attached patch adds basic support\nfor Type=notify-reload systemd services, that is, sends readiness\nnotifications on service reload. This allows waiting for postmaster\nreloa... |
[
{
"msg_contents": "Hi,\n\nI'm getting back to work on the index prefetching patch [1], but one\nannoying aspect of that patch is that it's limited to the context of a\nsingle executor node. It can be very effective when there's an index\nscan with many matches for a key, but it's entirely useless for plans\nwit... |
[
{
"msg_contents": "I'm somewhat expecting to be flamed to a well-done crisp for saying\nthis, but I think we need better ways for extensions to control the\nbehavior of PostgreSQL's query planner. I know of two major reasons\nwhy somebody might want to do this. First, you might want to do\nsomething like what p... |
[
{
"msg_contents": "Hi All,\n\nI've encountered a noticeable difference in execution time and query\nexecution plan row counts between PostgreSQL 13 and PostgreSQL 16 when\nrunning a query on information_schema tables. Surprisingly, PostgreSQL 16\nis performing slower than PostgreSQL 13.\n\nThe query executed on... |
[
{
"msg_contents": "Hello hackers,\n\nThis is an attempt to resurrect the thread [1] to throttle WAL inserts\nbefore the point of commit.\n\nBackground:\n\nTransactions on commit, wait for replication and make sure WAL is\nflushed up to commit lsn on standby, when synchronous_commit is on.\n\nWhile commit is a m... |
[
{
"msg_contents": "Hi hackers,\n\nWhen error \"trailing junk after numeric literal\" occurs at a number\nfollowed by a symbol that is presented by more than one byte, that symbol\nin the error message is not displayed correctly. Instead of that symbol\nthere is only its first byte. That makes the error message ... |
[
{
"msg_contents": "(creating new thread from [0])\n\nOn Wed, Apr 10, 2024 at 09:52:59PM -0400, Tom Lane wrote:\n> On fourth thought ... the number of tries to acquire the lock, or\n> in this case number of tries to observe the lock free, is not\n> NUM_DELAYS but NUM_DELAYS * spins_per_delay. Decreasing\n> spin... |
[
{
"msg_contents": "Hi hackers!\n\nRecently we faced issues with WAL recovery in our production. Issue\nreproduces not frequently, once in 1.5-2 month.\n\nSo, the problem looks like this in our production cluster logs:\n\nPostgresql startup process fails with signal 6.\n\"startup process (PID 369306) was termin... |
[
{
"msg_contents": "Hi,\n\nWhile testing a feature reported by Pavel in this thread[1] I realized\nthat elements containing whitespaces between them won't be indented with\nXMLSERIALIZE( ... INDENT)\n\nSELECT xmlserialize(DOCUMENT '<foo><bar>42</bar></foo>' AS text INDENT);\n\n xmlserialize \n----------------... |
[
{
"msg_contents": "These are ok:\n\nselect json_query('{\"a\": 1, \"b\": 42}'::jsonb, 'lax $.b' without wrapper);\n json_query\n------------\n 42\n\nselect json_query('{\"a\": 1, \"b\": 42}'::jsonb, 'lax $.b' with \nunconditional wrapper);\n json_query\n------------\n [42]\n\nBut this appears to be wrong:\n... |
[
{
"msg_contents": "Hi,\n\nI'm trying to create an Index Access Method Roting.\nBuilding the index requires iterating over all rows and calculating,\nwhich is then used during index construction.\n\nThe methods in the IndexAmRoutine seem to deal with insertion / index build\none row at a time.\nIs there any work... |
[
{
"msg_contents": "Hi,\n\nI would like to understand the pull_up_simple_values code a little bit more.\nPull-up of simple values was implemented in 2015 by commit f4abd02. In \nthe is_simple_values I see a check on the expression_returns_set() of \nthe RTE values list.\n\nBut since d43a619 in 2017 the check_srf... |
[
{
"msg_contents": "Hi,\n\nWhen working on the regex code I noticed that the labels of \nPG_Locale_Strategy had become inconsistent with the addition of \nPG_REGEX_BUILTIN but while at it I also noticed that \nPG_REGEX_LOCALE_WIDE_L and PG_REGEX_LOCALE_1BYTE_L did not make it\nobvious that they were libc-related... |
[
{
"msg_contents": "Hi hackers,\n\nThis patch introduces four new columns in pg_stat_database:\n\n* parallel_worker_planned\n* parallel_worker_launched\n* parallel_maint_worker_planned\n* parallel_maint_worker_launched\n\nThe intent is to help administrators evaluate the usage of parallel \nworkers in their data... |
[
{
"msg_contents": "Hi,\n\nSuppose you set compute_query_id=on and then execute a query using\neither the simple or the extended query protocol. With the simple\nquery protocol, the query ID is advertised during query execution;\nwith the extended query protocol, it's not. Here's a test case to\ndemonstrate:\n\n... |
[
{
"msg_contents": "Hi Hackers!\n\nThis would be version v1 of this feature\n\nBasically, the subject says it all: pl/pgperl Patch for being able to \ntell which function you're in.\nThis is a hashref so it will be possible to populate new and exciting \nother details in the future as the need arises\n\nThis als... |
[
{
"msg_contents": "Hi Hackers!\n\nThis would be version v1 of this feature\n\nBasically, the subject says it all: pl/pgperl Patch for being able to \ntell which function you're in.\nThis is a hashref so it will be possible to populate new and exciting \nother details in the future as the need arises\n\nThis als... |
[
{
"msg_contents": "\nUsually I see printtup in the perf-report with a noticeable ratio. Take\n\"SELECT * FROM pg_class\" for example, we can see:\n\n85.65% 3.25% postgres postgres [.] printtup\n\nThe high level design of printtup is:\n\n1. Used a pre-allocated StringInfo DR_printtup.buf to store data for... |
[
{
"msg_contents": "Our tool have detected that postgre in the version of REL9_6_18~ REL9_6_24\nmay also affected by the vulnerability CVE-2022-2625. The vulnerability\ndatabase does not include these versions and you may not fix it in the\nREL9_6 branch. Is there a need to backport the patch of CVE-2022-2625?... |
[
{
"msg_contents": "Hello,\n\nThis patch was a bit discussed on [1], and with more details on [2]. It\nintroduces four new columns in pg_stat_all_tables:\n\n* parallel_seq_scan\n* last_parallel_seq_scan\n* parallel_idx_scan\n* last_parallel_idx_scan\n\nand two new columns in pg_stat_all_indexes:\n\n* parallel_id... |
[
{
"msg_contents": "Hello Hackers,\n\nI’ve attached a patch to start adding SQL:2023 JSON simplified\naccessor support. This allows accessing JSON or JSONB fields using dot\nnotation (e.g., colname.field.field...), similar to composite types.\n\nCurrently, PostgreSQL uses nonstandard syntax like colname->x->y fo... |
[
{
"msg_contents": "Hi,\r\nwhen i read source code of the part of nbtree, i detected another kind of contradictory case postgresql has not eliminated \r\n(eg. x >4 and x <3) in the function _bt_preprocess_keys in nbtutils.c. this cause next unnecessary index scan and qual evaluation.\r\nit seems no one will writ... |
[
{
"msg_contents": "Currently, if you configure a hot standby server with a smaller \nmax_connections setting than the primary, the server refuses to start up:\n\nLOG: entering standby mode\nFATAL: recovery aborted because of insufficient parameter settings\nDETAIL: max_connections = 10 is a lower setting tha... |
[
{
"msg_contents": "Hello,\n\nThis patch was a bit discussed on [1], and with more details on [2]. It's\nbased on another patch sent in 2022 (see [3]). It introduces seven new\ncolumns in pg_stat_statements:\n\n * parallelized_queries_planned, number of times the query has been planned\nto be parallelized,\n * p... |
[
{
"msg_contents": "Hi hackers,\n\nI find there are some unnecessary load/store instructions being\nemitted by the JIT compiler.\n\nE.g.,\n\n```\nv_boolnull = l_load(b, TypeStorageBool, v_resnullp, \"\");\nv_boolvalue = l_load(b, TypeSizeT, v_resvaluep, \"\");\n\n/* set resnull to boolnull */\nLLVMBuildStore(b, ... |
[
{
"msg_contents": "H, hackersi! Tell me, please Do I understand correctly that\npg_dump/pg_restore has\nnot been taught to do COPY FREEZE when filling data? The last mention of\nthe plans was Bruce in 2013: https://postgrespro.com/list/thread-id/1815657\nhttps://paquier.xyz/postgresql-2/postgres-9-3-feature-hig... |
[
{
"msg_contents": "Hi,\n\nWhile looking at formatting.c file, I noticed a TODO about \"add support for\nroman number to standard number conversion\" (\nhttps://github.com/postgres/postgres/blob/master/src/backend/utils/adt/formatting.c#L52\n)\n\nI have attached the patch that adds support for this and converts... |
[
{
"msg_contents": "I normally wouldn't mention my blog entries here, but this one was about\nthe hackers mailing list, so wanted to let people know about it in case you\ndon't follow Planet Postgres. I scanned the last year's worth of posts and\ngathered the most used acronyms and jargon. The most commonly used... |
[
{
"msg_contents": "Hello Hackers,\n\nWhile working on inlining non-SQL SRFs [1] I noticed we don't have tests for when a PL/pgSQL \nfunction requires materialize mode but doesn't have a result TupleDesc. Here is a patch adding tests \nfor that, as well as some other conditions around SRF calls with `SETOF RECOR... |
[
{
"msg_contents": "Hello\n\nHere I present another attempt at making not-null constraints be\ncatalogued. This is largely based on the code reverted at 9ce04b50e120,\nexcept that we now have a not-null constraint automatically created for\nevery column of a primary key, and such constraint cannot be removed\nw... |
[
{
"msg_contents": "Hi hackers,\n\nThe nullness of casetest.value can be determined at the JIT compile\ntime. We can emit fewer codes by utilizing this property. The attached\npatch is trying to fix it.\n\nBest Regards,\nXing",
"msg_date": "Sat, 31 Aug 2024 16:04:40 +0800",
"msg_from": "Xing Guo <higuoxi... |
[
{
"msg_contents": "Hi,\n\nIt's been quite a while since the last version of the AIO patchset that I have\nposted. Of course parts of the larger project have since gone upstream [1].\n\nA lot of time since the last versions was spent understanding the performance\ncharacteristics of using AIO with WAL and under... |
[
{
"msg_contents": "adf97c156 added support to allow ExprStates to support hashing and\nadjusted Hash Join to make use of that. That allowed a speedup in hash\nvalue generation as it allowed JIT compilation of hash values. It also\nallowed more efficient tuple deforming as all required attributes are\ndeformed i... |
[
{
"msg_contents": "The following bug has been logged on the website:\n\nBug reference: 18598\nLogged by: Alexander Lakhin\nEmail address: exclusion@gmail.com\nPostgreSQL version: 17beta3\nOperating system: Ubuntu 22.04\nDescription: \n\nThe following query:\r\nSELECT JSON_OBJECTAGG(i... |
[
{
"msg_contents": "Hi hackers. While reviewing another thread I had cause to look at the\ndocs for the pg_replication_slot 'inactive_since' field [1] for the\nfirst time.\n\nI was confused by the description, which is as follows:\n----\ninactive_since timestamptz\nThe time since the slot has become inactive. NU... |
[
{
"msg_contents": "Hi,\nI have created my own output plugin for logical decoding.\nI am storing decoded data in Apache kafka via pg_recvlogical utility.\nUsing pg_recvlogical I am updating confirmed_flush_lsn of slot based on the\nvalue that I'm storing in kafka,this is done for every 10 secs.\n\nIn case of wal... |
[
{
"msg_contents": "While working on some other code I noticed that in\nFindReplTupleInLocalRel() there is an assert [1] that seems to be\npassing IndexRelation to GetRelationIdentityOrPK() whereas it should\nbe passing normal relation.\n\n[1]\nif (OidIsValid(localidxoid))\n{\n#ifdef USE_ASSERT_CHECKING\n Rel... |
[
{
"msg_contents": "There's a category[1] of random build farm/CI failures where Windows\nbehaves differently and our stuff breaks, which also affects end\nusers. A recent BF failure[2] that looks like one of those jangled my\nnerves when I pushed a commit, so I looked into a new theory on how to\nfix it. Firs... |
[
{
"msg_contents": "Hi,\n\nWhile reviewing another thread I was looking at the view\n'pg_stats_subscription_stats' view. In particular, I was looking at\nthe order of the \"*_count\" columns of that view.\n\nIMO there is an intuitive/natural ordering for the logical replication\noperations (LR) being counted. Fo... |
[
{
"msg_contents": "Hi hackers,\n\nPlease find attached a patch to implement $SUBJECT.\n\nWhile pg_stat_io provides cluster-wide I/O statistics, this patch adds a new\npg_my_stat_io view to display \"my\" backend I/O statistics and a new\npg_stat_get_backend_io() function to retrieve the I/O statistics for a giv... |
[
{
"msg_contents": "There are only a few (not necessarily thread-safe) strerror() calls in \nthe backend; most other potential users use %m in a format string.\n\nIn two cases, the reason for using strerror() was that we needed to \nprint the error message twice, and so errno has to be reset for the \nsecond tim... |
[
{
"msg_contents": "Hi all,\n\nCurrently, the backend-level initialization of pgstats happens in\npgstat_initialize(), where we are using a shortcut for the WAL stats,\nwith pgstat_init_wal().\n\nI'd like to propose to add a callback for that, so as in-core or\ncustom pgstats kinds can assign custom actions when... |
[
{
"msg_contents": "In [1] there was a short discussion about removing no-op\nPlaceHolderVars. This thread is for continuing that discussion.\n\nWe may insert PlaceHolderVars when pulling up a subquery that is\nwithin the nullable side of an outer join: if subquery pullup needs to\nreplace a subquery-referencin... |
[
{
"msg_contents": "Hi all,\n\nThe last TODO item I had in my bucket about the generalization of\npgstats is the option to a better control on the flush of the stats\ndepending on the kind for fixed-numbered stats. Currently, this is\ncontrolled by pgstat_report_stat(), that includes special handling for\nWAL, ... |
[
{
"msg_contents": "Hi\n\nI try to install devel package\n\n[student@localhost ~]$ LANG=C sudo dnf install postgresql15-devel\nLast metadata expiration check: 0:23:04 ago on Tue Sep 3 06:08:29 2024.\nError:\n Problem: cannot install the best candidate for the job\n - nothing provides perl(IPC::Run) needed by\n... |
[
{
"msg_contents": "Hi,\r\n\r\nI ran into an issue (previously discussed[1]; quoting Andres out of \r\ncontext that not addressing it then would \"[a]ll but guarantee that \r\nwe'll have this discussion again\"[2]) when trying to build a very large \r\nexpression index that did not fit within the page boundary. ... |
[
{
"msg_contents": "Hello hackers,\n(Cc people involved in the earlier discussion)\n\nI would like to discuss the $Subject.\n\nWhile discussing Logical Replication's Conflict Detection and\nResolution (CDR) design in [1] , it came to our notice that the\ncommit LSN and timestamp may not correlate perfectly i.e.... |
[
{
"msg_contents": "Hello,\n\nWhile reviewing a patch, I noticed that enum RecoveryTargetAction is\nstill in xlog_internal.h, even though it seems like it should be in\nxlogrecovery.h. Commit 70e81861fa separated out xlogrecovery.c/h and\nmoved several enums related to recovery targets to\nxlogrecovery.h. Howeve... |
[
{
"msg_contents": "Hi,\n\nIn the AIO patchset there are cases where we have to LOG failures inside a\ncritical section. This is necessary because e.g. a buffer read might complete\nwhile we are waiting for a WAL write inside a critical section.\n\nWe can't just defer the log message, as the IO might end up bein... |
[
{
"msg_contents": "Hi.\n\nPer coverity.\n\nI think that commit c582b75\n<https://github.com/postgres/postgres/commit/c582b75851c2d096ce050d753494505a957cee75>,\nleft an oversight.\n\nThe report is:\nCID 1559993: (#1 of 1): Logically dead code (DEADCODE)\n\nTrivial patch attached.\n\nbest regards,\nRanier Vilela... |
[
{
"msg_contents": "Hi.\n\nPer Coverity.\n\nI think that commit 6ebeeae\n<http://6ebeeae29626e742bbe16db3fa6fccf1186c0dfb> left out an oversight.\n\nThe report is:\nCID 1559991: (#1 of 1): Dereference null return value (NULL_RETURNS)\n\nThe function *findTypeByOid* can return NULL.\nIt is necessary to check the ... |
[
{
"msg_contents": "Hi.\n\nPer Coverity.\n\nThe commit 9758174 <http://9758174e2e5cd278cf37e0980da76b51890e0011>,\nincluded the source src/backend/replication/logical/conflict.c.\nThe function *errdetail_apply_conflict* reports potential conflicts.\nBut do not care about possible resource leaks.\nHowever, the le... |
[
{
"msg_contents": "Hi.\n\nPer Coverity.\n\nThe commit 7949d95 <http://7949d9594582ab49dee221e1db1aa5401ace49d4>, left\nout an oversight.\n\nThe report is:\nCID 1559468: (#1 of 1): Overflowed array index read (INTEGER_OVERFLOW)\n\nI think that Coverity is right.\nIn the function *pgstat_read_statsfile* It is nec... |
[
{
"msg_contents": "Hi,\r\n\r\nAttached is the draft of the PostgreSQL 17 release announcement. This is \r\na draft of the text that will go into the press kit, with the key \r\nportions to review starting from the top of the document, up until the \r\n\"About PostgreSQL\" section.\r\n\r\nPlease provide feedback... |
[
{
"msg_contents": "Hi,\n\nI need to assign role permissions from one role to another. However, after\ngranting the role, I see that the permission list for the target role has\nnot been updated. For this process, I followed the PostgreSQL documentation\navailable at PostgreSQL Role Membership\n<https://www.post... |
[
{
"msg_contents": "hi.\nWhile reviewing virtual generated columns,\nI find some issues with the updatable view interacting with stored\ngenerated columns.\n\n-----------------------\ndrop table if exists base_tbl cascade;\nCREATE TABLE base_tbl (a int, b int GENERATED ALWAYS AS (22) stored, d\nint default 22);\... |
[
{
"msg_contents": "The meson build currently does not produce llvm bitcode (.bc) files. \nAFAIK, this is the last major regression for using meson for production \nbuilds.\n\nIs anyone working on that? I vaguely recall that some in-progress code \nwas shared a couple of years ago, but I haven't seen anything s... |
[
{
"msg_contents": "Hi hackers,\n\nI am starting a new thread to discuss and propose the conflict detection for\nupdate_deleted scenarios during logical replication. This conflict occurs when\nthe apply worker cannot find the target tuple to be updated, as the tuple might\nhave been removed by another origin.\n\... |
[
{
"msg_contents": "hi.\none minor issue for ATExecColumnDefault comments.\n\n\n/*\n * ALTER TABLE ALTER COLUMN SET/DROP DEFAULT\n *\n * Return the address of the affected column.\n */\nstatic ObjectAddress\nATExecColumnDefault(Relation rel, const char *colName,\n Node *newDefault, LOCKMODE lo... |
[
{
"msg_contents": "Hi hackers,\n\nIt's quite common that poor query performance can be attributed to \ninaccurate row estimations by the planner. To make it easier to detect \nthese discrepancies, rather than scrutinizing the estimates manually, it \nwould be helpful to output a dedicated |NOTICE| message.\n\nI... |
[
{
"msg_contents": "Hi I am trying to install Postgresql 16 on my freebsd 14.1 by compiling it\nhosted in an ec2 machine on AWS.\n\nI am using GCC13 to compile the binaries and I keep on running into\n\n\n*gcc13: fatal error: cannot read spec file './specs': Is a directory *Please\nHelp\n\nhere is the code of my... |
[
{
"msg_contents": "Доброго дня, Повідомляємо Вас, що стосовно Вашої юридичної особи ведеться виконавче провадження за цивільним позовом. Вам необхідно з'явитись за адресою: просп. Шевченка, 29, Одеса, Одеська область 12.09.2024 до 11:30. \n\nПорядок денний та копія позовної заяви : scan_documet.pdf\n\nЗ поваг... |
[
{
"msg_contents": "Hi hackers,\n\nWhile working on the per backend I/O statistics patch ([1]), I noticed that\nthere is an unnecessary call to TimestampTzGetDatum() in pg_stat_get_io() (\nas the reset_time is already a Datum).\n\nPlease find attached a tiny patch to remove this unnecessary call.\n\n\n[1]: https... |
[
{
"msg_contents": "Hi,\n\nSince 1bb2558046c, XLogFileRead() doesn't use the emode argument. \nAlso, since abf5c5c9a4f, XLogFileReadAnyTLI() is called just once\nand emode is always DEBUG2. So, I think we can remove the emode\nargument from these functions. I've atached the patch.\n\nRegards,\nYugo Nagata\n\n-- ... |
[
{
"msg_contents": "Hello!\n\nWhile working on [1], I have found a small issue with correctness\nof set_indexsafe_procflags usage in ReindexRelationConcurrently introduced\nin [2].\n\n> idx->safe = (indexRel->rd_indexprs == NIL && indexRel->rd_indpred == NIL);\n\nIt is always true because there are no RelationGe... |
[
{
"msg_contents": "Hello hackers,\n\nWhile trying to reproduce a recent fairywren (a Windows animal) failure,\nI ran amcheck/amcheck/003_cic_2pc in parallel inside a slowed-down\nVM and came across another issue:\n### Stopping node \"CIC_2PC_test\" using mode fast\n# Running: pg_ctl -D C:\\src\\postgresql\\buil... |
[
{
"msg_contents": "Some days ago Tom Lane said ...\n\nSELECT events & 4 != 0 AS can_upd, events & 8 != 0 AS can_ins, events & 16\n!= 0 AS can_del FROM\npg_catalog.pg_relation_is_updatable('_pessoa'::regclass, false) t(events);\n\nWell, I didn't find that function on DOCs and then I thought, are there\nother fun... |
[
{
"msg_contents": "Hi all, I found that there is a race condition between two global transaction, which may cause instance\r\nrestart failed with error 'could not access status of transaction xxx\",\"Could not open file \"\"pg_xact/xxx\"\": No such file or directory'.\r\n\r\n\r\n ... |
[
{
"msg_contents": "Basically, when we are inserting into a leaf relation (or lower level\nrelation of the partitioned relation), we acquire the lock on the leaf\nrelation during parsing time itself whereas parent lock is acquire\nduring generate_partition_qual(). Now concurrently if we try to drop\nthe partiti... |
[
{
"msg_contents": "Dear hackers,\n\nI'm the maintainer of ruby-pg the ruby interface to the PostgreSQL \ndatabase. This binding uses the asynchronous API of libpq by default to \nfacilitate the ruby IO wait and scheduling mechanisms.\n\nThis works well with the vanilla postgresql server, but it leads to \nstarv... |
[
{
"msg_contents": "Over in the thread about teaching to_number() to handle Roman\nnumerals [1], it was noted that we currently have precisely zero\ntest coverage for to_char()'s existing Roman-numeral code, except\nin the timestamp code path which shares nothing with the numeric\ncode path.\n\nIn looking at thi... |
[
{
"msg_contents": "In rescanLatestTimeLine(), if a new target timeline is found, expectedTLEs is \nreplaced with newExpectedTLEs that is newly allocated by readTimeLineHistory(),\nand old expectedTLEs is released using list_free_deep().\n\nHowever, if the current timeline is not part of the history of the new t... |
[
{
"msg_contents": "While looking at label_sort_with_costsize() due to another issue, I\nnoticed that we build explicit Sort nodes but not explicit Incremental\nSort nodes. I wonder why this is the case. It seems to me that\nIncremental Sorts are preferable in some cases. For example:\n\ncreate table t (a int... |
[
{
"msg_contents": "Hi\n\nI try new Fedora 41. Build fails\n\necho 'Name: libpq' >>libpq.pc\necho 'Description: PostgreSQL libpq library' >>libpq.pc\necho 'URL: https://www.postgresql.org/' >>libpq.pc\necho 'Version: 18devel' >>libpq.pc\necho 'Requires: ' >>libpq.pc\necho 'Requires.private: libssl, libcrypto' >>... |
[
{
"msg_contents": "I'm the maintainer of the PL/Haskell language extension. (\nhttps://github.com/ed-o-saurus/PLHaskell/)\n\nI want to be able to have a function received and/or return numeric data.\nHowever, I'm having trouble getting data from Datums and building Datums to\nreturn. numeric.h does not contain ... |
[
{
"msg_contents": "Commit a70e01d430 removed support for OpenSSL 1.0.2 in order to simplify the\ncode by removing the need for finicky initialization of the library. Based on\nour API usage the new minimum version was defined as 1.1.0.\n\nThe patchset in https://commitfest.postgresql.org/49/5025/ which adds su... |
[
{
"msg_contents": "Hi,\n\nIn v8.2, the RULE privilege for tables was removed, but for backward compatibility,\nGRANT/REVOKE RULE, has_table_privilege(..., 'RULE') etc are still accepted,\nthough they don't perform any actions.\n\nDo we still need to maintain this backward compatibility?\nCould we consider remov... |
[
{
"msg_contents": "Hi all,\n\npg_utf8_string_len() doesn't check the remaining string length before\ncalling pg_utf8_is_legal(), so there's a possibility of jumping a\ncouple of bytes past the end of the string. (The overread stops there,\nbecause the function won't validate a sequence containing a null\nbyte.)... |
[
{
"msg_contents": "Hi,\n\nALTER_REPLICATION_SLOT on invalidated replication slots is unnecessary\nas there is no way to get the invalidated (logical) slot to work.\nPlease find the patch to add an error in such cases. Relevant\ndiscussion is at [1].\n\nThoughts?\n\n[1] https://www.postgresql.org/message-id/CAA4... |
[
{
"msg_contents": "Hello hackers,\n\nThis is my first time posting here, and I’d like to propose a new feature\nrelated to PostgreSQL indexes. If this idea resonates, I’d be happy to\nfollow up with a patch as well.\n\n*Problem*:\nAdding and removing indexes is a common operation in PostgreSQL. On larger\ndatab... |
[
{
"msg_contents": "hi,\none minor issue. not that minor,\nsince many DDLs need to consider the system attribute.\n\nlooking at these functions:\nSearchSysCacheCopyAttName\nSearchSysCacheAttName\nget_attnum\n\nget_attnum says:\nReturns InvalidAttrNumber if the attr doesn't exist (or is dropped).\n\nSo I conclude... |
[
{
"msg_contents": "In some cases, we may want to transfer a HAVING clause into WHERE in\nhopes of eliminating tuples before aggregation instead of after.\n\nPreviously, we couldn't do this if there were any nonempty grouping\nsets, because we didn't have a way to tell if the HAVING clause\nreferenced any column... |
[
{
"msg_contents": "At the end of SetupLockInTable(), there is a check for the \"lock already\nheld\" error.\nBecause the nRequested and requested[lockmode] value of a lock is bumped\nbefore \"lock already held\" error, and there is no way to reduce them later\nfor\nthis situation, then it will keep the inconsis... |
[
{
"msg_contents": "Hi,\r\n\r\nCurrently, in the pg_stat_io view, IOs are counted as blocks. However,\r\nthere are two issues with this approach:\r\n\r\n1- The actual number of IO requests to the kernel is lower because IO\r\nrequests can be merged before sending the final request. Additionally, it\r\nappears th... |
[
{
"msg_contents": "Hi hackers,\n\nWhile working on a new pg_logicalinspect module ([1]), I reached a point where\nall the CI tests were green except the compiler warnings one. Then, to save time\naddressing the issue, I modified the .cirrus.tasks.yml file to $SUBJECT.\n\nI think this could be useful for others ... |
[
{
"msg_contents": "Hi,\n\nCommit 4ed8f0913bfd introduced long SLRU file names. The proposed\npatch removes SlruCtl->long_segment_names flag and makes SLRU always\nuse long file names. This simplifies both the code and the API.\nCorresponding changes to pg_upgrade are included.\n\nOne drawback I see is that tech... |
[
{
"msg_contents": "Hi,\n\nDuring the PGDAY.Spain'2024 Yurii Rashkovskii found out boring behaviour \nrelated to functions versioning:\nIf you open a transaction in one session and execute the function, then \nreplace this function with a new version or drop it in a concurrent \nsession; the first session doesn'... |
[
{
"msg_contents": "Hi all,\n\nWe have several reports that logical decoding uses memory much more\nthan logical_decoding_work_mem[1][2][3]. For instance in one of the\nreports[1], even though users set logical_decoding_work_mem to\n'256MB', a walsender process was killed by OOM because of using more\nthan 4GB m... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.