threads listlengths 1 2.99k |
|---|
[
{
"msg_contents": "I have noticed, if query comes from PostgreSQL JDBC Driver, then query_id\nis not present in pg_stat_activity. Erik Wienhold figured out that reason\ncan be in extended query protocol (\nhttps://www.postgresql.org/message-id/1391613709.939460.1684777418070@office.mailbox.org\n)\nMy question ... |
[
{
"msg_contents": "Hi,\n\nI noticed that these two function, introduced in d746021de18b, disagree\non what types they support. For construct_array_builtin, we support\nthese types:\n\n - CHAROID:\n - CSTRINGOID:\n - FLOAT4OID:\n - INT2OID:\n - INT4OID:\n - INT8OID:\n - NAMEOID:\n - OIDOID:\n - REGTYPEOID:\n - T... |
[
{
"msg_contents": "Hi!\n\nTL;DR:\n\nCLANG is used to compile *.bc files during postgresql build. Is it OK to have a different compiler for the rest of the build? gcc, or even another version of clang?\n\n--\n\nSlightly longer version:\n\nI'm packaging postgresql for FreeBSD and as you probably know, in that OS ... |
[
{
"msg_contents": "Hi!\n\nTL;DR:\n\nCLANG is used to compile *.bc files during postgresql build. Is it OK to have a different compiler for the rest of the build? gcc, or even another version of clang?\n\n--\n\nSlightly longer version:\n\nI'm packaging postgresql for FreeBSD and as you probably know, in that OS ... |
[
{
"msg_contents": "Hi,\n When join two table on multiple columns equaljoin, rows estimation always use selectivity = multiplied by distinct multiple individual columns, possible to use extended n-distinct statistics on multiple columns?\n PG v14.8-1, attached please check test case with details.\n\nThan... |
[
{
"msg_contents": "It's annoyed me for some time that to_timestamp() doesn't implement\nthe TZ format code that to_char() has. I finally got motivated to\ndo something about that after the complaint at [1] that jsonpath's\ndatetime() method can't read typical JSON.stringify() output like\n\"2023-05-22T03:09:37... |
[
{
"msg_contents": "Hi,\n\nI just helped somebody debug a postgres performance problem that turned out to\nbe not actually be postgres' fault. It turned out to be because postgres'\nstdout/stderr were piped to a program, and that program was slow. Whenever the\npipe buffer filled up, postgres stopped making pro... |
[
{
"msg_contents": "Hi,\n\nI've attached the patch for $subject. In the following comment,\n\n /*\n * If available and useful, use posix_fallocate() (via FileAllocate())\n * to extend the relation. That's often more efficient than using\n * write(), as it commonly won't cause the ke... |
[
{
"msg_contents": "\nHi, hackers\n\nWe use (GUC_UNIT_MEMORY | GUC_UNIT_TIME) instead of GUC_UNIT even though we\nalready define it in guc.h.\n\nMaybe using GUC_UNIT is better? Here is a patch to fix it.\n\ndiff --git a/src/backend/utils/misc/guc.c b/src/backend/utils/misc/guc.c\nindex a9033b7a54..5308896c87 10... |
[
{
"msg_contents": "Like in cost_seqscan(), I'd expect the subpath cost to be divided among\nparallel workers. The patch below shows what I mean. Am I right?\n\n-- \nAntonin Houska\nWeb: https://www.cybertec-postgresql.com",
"msg_date": "Wed, 14 Jun 2023 14:36:54 +0200",
"msg_from": "Antonin Houska <ah@c... |
[
{
"msg_contents": "A few years ago, I sketched out a design for incremental backup, but\nno patch for incremental backup ever got committed. Instead, the whole\nthing evolved into a project to add backup manifests, which are nice,\nbut not as nice as incremental backup would be. So I've decided to\nhave another... |
[
{
"msg_contents": "The locale \"C\" (and equivalently, \"POSIX\") is not really a libc locale;\nit's implemented internally with memcmp for collation and\npg_ascii_tolower, etc., for ctype.\n\nThe attached patch implements a new collation provider, \"builtin\",\nwhich only supports \"C\" and \"POSIX\". It does ... |
[
{
"msg_contents": "Hello,\n\nThere is often a need to test particular queries executed in the worst-case\nscenario, i.e. right after a server restart or with no or minimal amount of\ndata in shared buffers. In Postgres it's currently hard to achieve (other\nthan to restart the server completely to run a single ... |
[
{
"msg_contents": "Hi,\n\nThere are different types of Logical Replication workers -- e.g.\ntablesync workers, apply workers, and parallel apply workers.\n\nThe logging and errors often name these worker types, but during a\nrecent code review, I noticed some inconsistency in the way this is\ndone:\na) there is... |
[
{
"msg_contents": "Currently, CREATE COLLATION always defaults the provider to libc.\n\nThe attached patch causes it to default to libc if LC_COLLATE/LC_CTYPE\nare specified, otherwise default to the current database default\ncollation's provider.\n\nThat way, the provider choice at initdb time then becomes the... |
[
{
"msg_contents": "Hi,\n\nCurrently, only one PG_WAIT_EXTENSION event can be used as a\nwait event for extensions. Therefore, in environments with multiple\nextensions are installed, it could take time to identify which\nextension is the bottleneck.\n\nSo, I'd like to support new APIs to define custom wait even... |
[
{
"msg_contents": "Hi all,\n\nWhile doing some tests with the tree, I have noticed that we don't do\nin the tests of unaccent the business that we have elsewhere\n(test_regex, fuzzystrmatch, now hstore, collation tests, etc.) to make\nthe tests portable when these tests include UTF-8 characters but the\nregress... |
[
{
"msg_contents": "Dear hackers,\n\nI have noticed that the testcase subscription/033_run_as_table_owner in the\nsubscription is not executed when meson build system is chosen. The case is not\nlisted in the meson.build.\n\nDo we have any reasons or backgrounds about it?\nPSA the patch to add the case. It works... |
[
{
"msg_contents": "As discussed [1 ][2] currently, the checkpoint-redo LSN can not be\naccurately detected while processing the WAL. Although we have a\ncheckpoint WAL record containing the exact redo LSN, other WAL records\nmay be inserted between the checkpoint-redo LSN and the actual\ncheckpoint record. If w... |
[
{
"msg_contents": "Hi,\n\nI've attached the patch for the following rewriteTargetView comments.\n\n\n Assert(parsetree->resultRelation == new_rt_index);\n\n /*\n * For INSERT/UPDATE we must also update resnos in the targetlist to refer\n * to columns of the base relation, since those indicate the ta... |
[
{
"msg_contents": "Hi, all.\n\nSome of my clients use JOIN's with three - four clauses. Quite \nfrequently, I see complaints on unreasonable switch of JOIN algorithm to \nMerge Join instead of Hash Join. Quick research have shown one weak \nplace - estimation of an average bucket size in final_cost_hashjoin (se... |
[
{
"msg_contents": "Hi,\n\nI noticed that 2f2b18bd3f55 forgot to remove the mention of\nparse_jsontable.c in src/backend/parser/README.\n\nAttached a patch to fix that. Will push that shortly to HEAD and v15.\n\n-- \nThanks, Amit Langote\nEDB: http://www.enterprisedb.com",
"msg_date": "Thu, 15 Jun 2023 18:5... |
[
{
"msg_contents": "Good day, hackers.\n\nI found, than declaration of function as IMMUTABLE/STABLE is not enough to be sure\nfunction doesn't manipulate data.\n\nIn fact, SPI checks only direct function kind, but fails to check indirect call.\n\nAttached immutable_not.sql creates 3 functions:\n\n- `immutable_di... |
[
{
"msg_contents": "ExecIncrementalSort() calls tuplesort_begin_common(), which creates the \"TupleSort main\"\nand \"TupleSort sort\" memory contexts, and ExecEndIncrementalSort() calls tuplesort_end(),\nwhich destroys them.\nBut ExecReScanIncrementalSort() only resets the memory contexts. Since the next call ... |
[
{
"msg_contents": "Hi,\r\n\r\nIn the function WalReceiverMain, when the function walrcv_create_slot is called,\r\nthe fourth parameter is assigned the value \"0\" instead of the enum value\r\n\"CRS_EXPORT_SNAPSHOT\". I think it would be better to use the corresponding enum\r\nvalue.\r\n\r\nAttach the patch to c... |
[
{
"msg_contents": "We have a small table with only 23 rows and 21 values.\n\nThe resulting MCV and histogram is as follows\nstanumbers1 | {0.08695652,0.08695652}\nstavalues1 | {v1,v2}\nstavalues2 | \n{v3,v4,v5,v6,v7,v8,v9,v10,v11,v12,v13,v14,v15,v16,v17,v18,v19,v20,v21}\n\nAn incorrect number of rows was esti... |
[
{
"msg_contents": "Hi hackers,\n\nRelcache errors from time to time detect catalog corruptions. For example, recently I observed following:\n1. Filesystem or nvme disk zeroed out leading 160Kb of catalog index. This type of corruption passes through data_checksums.\n2. RelationBuildTupleDesc() was failing with ... |
[
{
"msg_contents": "Hi hackers,\n\npg_get_backend_memory_contexts() (and pg_backend_memory_contexts view)\ndoes not display parent/child relation between contexts reliably.\nCurrent version of this function only shows the name of parent context\nfor each context. The issue here is that it's not guaranteed that\n... |
[
{
"msg_contents": "Hey everyone,\n\nI've discovered a serious bug that leads to a server crash upon promoting an instance that crashed previously and did\nrecovery in standby mode.\n\nThe bug is present in PostgreSQL versions 13 and 14 (and in earlier versions, though it doesn't manifest itself so\ncatastrophic... |
[
{
"msg_contents": "Patch attached. Currently, the Makefile specifies NO_LOCALE=1, and the\nmeson.build does not.\n\n\n-- \nJeff Davis\nPostgreSQL Contributor Team - AWS",
"msg_date": "Fri, 16 Jun 2023 13:29:18 -0700",
"msg_from": "Jeff Davis <pgsql@j-davis.com>",
"msg_from_op": true,
"msg_subjec... |
[
{
"msg_contents": "Hi,\n\nI am proposing that the default value of\nclient_connection_check_interval be moved to a non-zero value on\nsystems where it is supported. I think it would be a nice quality of\nlife improvement. I have run into a problem where this would have been\nuseful before with regard to pgbench... |
[
{
"msg_contents": "Attached patch adds additional hardening to nbtree page deletion. It\nmakes nbtree VACUUM tolerate a certain sort of cross-page\ninconsistencies in the structure of an index (corruption). VACUUM can\npress on, avoiding an eventual wraparound/xidStopLimit failure in\nenvironments where nobody ... |
[
{
"msg_contents": "Hi hackers,\n\nIn modern versions of Postgres the dollar sign is a totally legal character\nfor identifiers (except for the first character), but tab-complete do not\ntreat such identifiers well.\nFor example if one try to create an Oracle-style view like this:\n\ncreate view v$activity as se... |
[
{
"msg_contents": "Hi All,\n\nI've written a patch to add hash functions for the ltree extension. It adds\nsupport for hash indexes and hash aggregation. I've reused the existing\nlogic that's used to hash arrays and added tests that mirror elsewhere\n(i.e. hstore and hash_func regression tests).\n\nThe patch d... |
[
{
"msg_contents": "Hi,\r\n\r\nThe release date for PostgreSQL 16 Beta 2 is June 29, 2023. Please be \r\nsure to commit any open items[1] for the Beta 2 release before June 25, \r\n2023 0:00 AoE[2] to give them enough time to work through the buildfarm.\r\n\r\nThanks,\r\n\r\nJonathan\r\n\r\n[1] \r\nhttps://wiki.... |
[
{
"msg_contents": "Hi,\n\nI have been testing 16beta1, last commit\na14e75eb0b6a73821e0d66c0d407372ec8376105\nI just let sqlsmith do its magic before trying something else, and\ntoday I found a core with the attached backtrace.\n\nOnly information on the log was this:\n\nDETAIL: Failed process was running: aut... |
[
{
"msg_contents": "Has anyone recently tried updating a streaming replication cluster using\ndebian’s pg_upgradecluster(1) on each node?\n\nDid things work well?\n\nMy last attempt (11 to 13, as I recall) had issues and I had to drop and\nre-install the db on the secondaries.\n\nI'd like to avoid that this time... |
[
{
"msg_contents": "I started to look at the code in postmaster.c related to launching child \nprocesses. I tried to reduce the difference between EXEC_BACKEND and \n!EXEC_BACKEND code paths, and put the code that needs to differ behind a \nbetter abstraction. I started doing this to help with implementing \nmul... |
[
{
"msg_contents": "Hello,\n\nOver in \"Parallelize correlated subqueries that execute within each\nworker\" [1} Richard Guo found a bug in the current version of my patch\nin that thread. While debugging that issue I've been wondering why\nPath's param_info field seems to be NULL unless there is a LATERAL\nrefe... |
[
{
"msg_contents": "Hello.\n\nI'm starting a new thread for $subject per Alvaro's suggestion at [1].\n\nSo the following sql/json things still remain to be done:\n\n* sql/json query functions:\n json_exists()\n json_query()\n json_value()\n\n* other sql/json functions:\n json()\n json_scalar()\n ... |
[
{
"msg_contents": "Hi all,\n\nthis is about a limitation of the current query planner implementation \nwhich causes big performance declines for certain types of queries. \nAffected queries will typically execute about 1000 times slower than \nthey could. Examples are given below.\n\nAfter talking about this wi... |
[
{
"msg_contents": "An important goal of the work on nbtree that went into PostgreSQL 12\n(and to a lesser extent the work that went into 13) was to make sure\nthat index scans deal with \"boundary cases\" optimally. The simplest\nway of explaining what this means is through a practical worked\nexample.\n\nRecap... |
[
{
"msg_contents": "MERGE is now a data-modification command too.",
"msg_date": "Mon, 19 Jun 2023 23:32:46 -0700",
"msg_from": "Will Mortensen <will@extrahop.com>",
"msg_from_op": true,
"msg_subject": "[PATCH] doc: add missing mention of MERGE in MVCC"
},
{
"msg_contents": "On Mon, Jun 19... |
[
{
"msg_contents": "\nStatus on collation loose ends:\n\n1. There's an open item \"Switch to ICU for 17\". It's a little bit\nconfusing exactly what that means, and the CF entry refers to two\nitems, one of which is the build-time default to --with-icu. As far as\nI know, building with ICU by default is a settle... |
[
{
"msg_contents": "Hi,\n\nAs I've mentioned earlier on-list [0][1] and off-list, I've been\nworking on reducing the volume of WAL that we write. This is one\nintermediate step towards that effort.\n\nAttached is a patchset that reduces the storage overhead of each WAL\nrecord, with theoretical total savings in ... |
[
{
"msg_contents": "Hi all,\n(adding Daniel in CC.)\n\nCompiling Postgres up to 13 with OpenSSL 3.0 leads to a couple of\ncompilation warnings with what OpenSSL considers as deprecated, like:\nsha2_openssl.c: In function pg_sha384_init\nsha2_openssl.c:70:9: warning: SHA384_Init is deprecated =\nSince OpenSSL 3.0... |
[
{
"msg_contents": "I define a table user_ranks as such:\n\nCREATE TABLE user_ranks (\n id INTEGER GENERATED ALWAYS AS IDENTITY PRIMARY KEY,\n rank INTEGER NOT NULL,\n CONSTRAINT \"by (rank, id)\" UNIQUE (rank, id)\n);\n\nINSERT INTO user_ranks (user_id, rank) SELECT generate_series(1, 10000),\ngenerate_serie... |
[
{
"msg_contents": "Hi all,\n(Adding Evan in CC as he has reported the original issue with hstore.)\n\n$subject has showed up as a subject for discussion when looking at the\nset of whitespace characters that we use in the parsers:\nhttps://www.postgresql.org/message-id/CA+HWA9bTRDf52DHyU+JOoqEALgRGRo5uHUYTFuduo... |
[
{
"msg_contents": "Hi hackers,\n\nPlease find attached a patch to truncate (in ProcessStartupPacket())\nthe port->database_name and port->user_name in such a way to not break\nmultibyte character boundary.\n\nIndeed, currently, one could create a database that way:\n\npostgres=# create database ääääääääääääääää... |
[
{
"msg_contents": "Hi,\r\n\r\nI was trying to add WAL stats to pg_stat_io. While doing that I was\r\ncomparing pg_stat_wal and pg_stat_io's WAL stats and there was some\r\ninequality between the total number of WALs. I found that the difference\r\ncomes from bgwriter's WALs. bgwriter generates WAL but it doesn'... |
[
{
"msg_contents": "Hi,\n\nDavid Rowley wrote:\n>I've adjusted the attached patch to do that.\n\nI think that was room for more improvements.\n\n1. bms_member_index Bitmapset can be const.\n2. Only compute BITNUM when necessary.\n3. Avoid enlargement when nwords is equal wordnum.\n Can save cycles when in cor... |
[
{
"msg_contents": "Hello,\n\nWhile at PGCon I was chatting with Andres (and I think Peter G. and a\nfew others who I can't remember at the moment, apologies) and Andres\nnoted that while we opportunistically prune a page when inserting a\ntuple (before deciding we need a new page) we don't do the same for\nupda... |
[
{
"msg_contents": " Hi,\n\nIn the \"Order changes in PG16 since ICU introduction\" discussion, one\nsub-thread [1] was about having a credible use case for tailoring collations\nwith custom rules, a new feature in v16.\n\nAt a conference this week I was asked if ICU could be able to\nsort like EBCDIC [2]. It tu... |
[
{
"msg_contents": "Hi all,\n\nI briefly mentioned this issue in another mailing thread [0].\n\nCurrently, a user is allowed to execute SET SESSION AUTHORIZATION [1]\nif the role they connected to PostgreSQL with was a superuser at the\ntime of connection. Even if the role is later altered to no longer be a\nsup... |
[
{
"msg_contents": "Hi,\n\nWhen vac_truncate_clog() returns early, due to one of these paths:\n\n\t/*\n\t * Do not truncate CLOG if we seem to have suffered wraparound already;\n\t * the computed minimum XID might be bogus. This case should now be\n\t * impossible due to the defenses in GetNewTransactionId, but... |
[
{
"msg_contents": "Dear hackers,\r\n(CC: Önder because he owned the related thread)\r\n\r\nThis is a follow-up thread of [1]. The commit allowed subscribers to use indexes\r\nother than PK and REPLICA IDENTITY when REPLICA IDENTITY is FULL on publisher,\r\nbut the index must be a B-tree. In this proposal, I aim... |
[
{
"msg_contents": "Hello, \n\nFollowing some conversation with Tomas at PGCon, I decided to resurrect this \ntopic, which was previously discussed in the context of moving tuplesort to \nuse GenerationContext: https://www.postgresql.org/message-id/\n8046109.NyiUUSuA9g%40aivenronan\n\nThe idea for this patch is ... |
[
{
"msg_contents": "Hi,\r\n\r\n[1] is a ready-for-committer enhancement to pg_stat_progress_vacuum which exposes\r\nthe total number of indexes to vacuum and how many indexes have been vacuumed in\r\nthe current vacuum cycle.\r\n\r\nTo even further improve visibility into index vacuuming, it would be beneficial ... |
[
{
"msg_contents": "Hi All,\n\nI've attached a couple of patches to allow ALTER OPERATOR to add\ncommutators, negators, hashes and merges to operators that lack them.\n\nThe need for this arose adding hash functions to the ltree type after the\noperator had been created without hash support[1]. There are potenti... |
[
{
"msg_contents": "Nearby I dissed psql's \\du command for its incoherent \"Attributes\"\ncolumn [1]. It's too late to think about changing that for v16,\nbut here's some things I think we should consider for v17:\n\n* It seems weird that some attributes are described in the negative\n(\"Cannot login\", \"No i... |
[
{
"msg_contents": "Hi hackers.\n\n_bt_readpage performs key check for each item on the page trying to \nlocate upper boundary.\nWhile comparison of simple integer keys are very fast, comparison of \nlong strings can be quite expensive.\nWe can first make check for the largest key on the page and if it is not \n... |
[
{
"msg_contents": "Hi\n\nMild corner-case annoyance while doing Random Experimental Things:\n\n postgres=# SELECT * FROM parttest;\n ERROR: user mapping not found for \"postgres\"\n\nOkaaaay, but which server?\n\n postgres=# \\det\n List of foreign tables\n Schema | Table | Ser... |
[
{
"msg_contents": "Hi,\n\nI need to move some databases from a MySQL server to Postgresql.\n\nCan someone tell me the migration procedure, tools, and recommendations?\n\nThanks\n\nHi,I need to move some databases from a MySQL server to Postgresql.Can someone tell me the migration procedure, tools, and recommend... |
[
{
"msg_contents": "Dear hackers,\n\nWhile discussing based on the article[1] with Japanese developers, \nI found inconsistencies between codes and documents.\n\n45b1a67a[2] changed the behavior when non-ASCII characters was set as application_name,\ncluster_name and postgres_fdw.application_name, but it seemed ... |
[
{
"msg_contents": "Hello,\n\nWe recently brought online a new database cluster, and in the course\nof ramping up traffic to it encountered a situation where a misplanned\nquery (analyzing helped with this, but I think the issue is still\nrelevant) resulted in that query being compiled with JIT, and soon a\nlarg... |
[
{
"msg_contents": "Hi,\n\nI ran into a pretty terrible case of LEFT JOIN estimate, resulting in\npretty arbitrary underestimate. The query is pretty trivial, nothing\noverly complex, and the more I think about it the more I think this is\na fairly fundamental flaw in how we estimate this type of joins.\n\nImagi... |
[
{
"msg_contents": "Hello hackers,\n\nCurrently domain casts are ignored. Yet this would be very useful for\nrepresenting data in different formats such as json.\n\nLet's take a tsrange as an example. Its json output by default:\n\nselect to_json('(2022-12-31 11:00, 2023-01-01 06:00)'::tsrange);\n ... |
[
{
"msg_contents": "Hi everyone!\n\nI am new to PostgreSQL community and working currently on project\npg_adviser [https://github.com/DrPostgres/pg_adviser/]\n\nThe extension last worked with version 8.3, and currently I am working to\nmake it support version 16 and then the other active versions.\n\nI will give... |
[
{
"msg_contents": "Attached is a PoC patch to implement \"Row pattern recognition\" (RPR)\nin SQL:2016 (I know SQL:2023 is already out, but I don't have access\nto it). Actually SQL:2016 defines RPR in two places[1]:\n\n Feature R010, “Row pattern recognition: FROM clause”\n Feature R020, “Row pattern rec... |
[
{
"msg_contents": "Hi,\n\nYuya Watari presented a series of patches, with the objective of improving\nthe Bitmapset [1].\nAfter reading through the patches, I saw a lot of good ideas and thought\nI'd help.\nUnfortunately, my suggestions were not well received.\nEven so, I decided to work on these patches and se... |
[
{
"msg_contents": "Hi all,\n\nJoe has reported me offlist that JumbleQuery() includes a dependency\nto the query text, but we don't use that anymore as the query ID is\ngenerated from the Query structure instead.\n\nAny thoughts about the cleanup attached? But at the same time, this\nis simple and a new thing,... |
[
{
"msg_contents": "This is a small code cleanup patch.\n\nSeveral commands internally assemble command lines to call other \ncommands. This includes initdb, pg_dumpall, and pg_regress. (Also \npg_ctl, but that is different enough that I didn't consider it here.) \nThis has all evolved a bit organically, with ... |
[
{
"msg_contents": "Hi All,\nEvery pg_decode routine except pg_decode_message that decodes a\ntransactional change, has following block\n/* output BEGIN if we haven't yet */\nif (data->skip_empty_xacts && !txndata->xact_wrote_changes)\n{\npg_output_begin(ctx, data, txn, false);\n}\ntxndata->xact_wrote_changes =... |
[
{
"msg_contents": "hi. simple question....\n\nThe following one works.\n------------------------------------------------------------\nDatum\ntest_direct_inputcall(PG_FUNCTION_ARGS)\n{\n char *token = PG_GETARG_CSTRING(0);\n Datum numd;\n if (!DirectInputFunctionCallSafe(numeric_in, token,\n ... |
[
{
"msg_contents": "Hello,\n\nThis attached patch enables pgbench to cancel queries during benchmark.\n\nFormerly, Ctrl+C during benchmark killed pgbench immediately, but backend\nprocesses executing long queries remained for a while. You can simply\nreproduce this problem by cancelling the pgbench running a cus... |
[
{
"msg_contents": "Hi hackers,\n\nIn memory contexts, block and chunk sizes are likely to be limited by\nsome upper bounds. Some examples of those bounds can be\nMEMORYCHUNK_MAX_BLOCKOFFSET and MEMORYCHUNK_MAX_VALUE. Both values are\nonly 1 less than 1GB.\nThis makes memory contexts to have blocks/chunks with s... |
[
{
"msg_contents": "Hello,\n\nHave we ever discussed running an analyze immediately after creating a table?\n\nConsider the following:\n\ncreate table stats(i int, t text not null);\nexplain select * from stats;\n Seq Scan on stats (cost=0.00..22.70 rows=1270 width=36\nanalyze stats;\nexplain select * from st... |
[
{
"msg_contents": "Hi,\n\nI played around with adding\n __attribute__((malloc(free_func), malloc(another_free_func)))\nannotations to a few functions in pg. See\nhttps://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html\n\n\nAdding them to pg_list.h seems to have found two valid issues when compiling\... |
[
{
"msg_contents": "Hello,\n\nI was running the test_pg_dump extension suite, and I got annoyed that\nI couldn't keep it from deleting its dump artifacts after a successful\nrun. Here's a patch to make use of PG_TEST_NOCLEAN (which currently\ncovers the test cluster's base directory) with the Test::Utils\ntempdi... |
[
{
"msg_contents": "Hi,\n\nOn Twitter Thomas thoroughly nerdsniped me [1]. As part of that I ran a\nconcurrent readonly pgbench workload and analyzed cacheline \"contention\" using\nperf c2c.\n\nOne of the cacheline conflicts, by far not the most common, but significant,\nis one I hadn't noticed in the past. The... |
[
{
"msg_contents": "Hi,\n\nAs mentioned nearby [1], Thomas brought up [2] the idea of using\nReadRecentBuffer() _bt_getroot(). I couldn't resist and prototyped it.\n\nUnfortunately it scaled way worse at first. This is not an inherent issue, but\ndue to an implementation choice in ReadRecentBuffer(). Whereas t... |
[
{
"msg_contents": "Hi,\n\nThe attached query makes beta2 crash with attached backtrace.\nInterestingly the index on ref_6 is needed to make it crash, without\nit the query works fine.\n\n-- \nJaime Casanova\nDirector de Servicios Profesionales\nSYSTEMGUARDS - Consultores de PostgreSQL",
"msg_date": "Mon, 26... |
[
{
"msg_contents": "Hi,\n\nCommit 6b4d23feef introduces a toplevel field in pgssHashKey, which leads\npadding. In pgss_store(), it comments that memset() is required when\npgssHashKey is without padding only.\n\n@@ -1224,9 +1227,14 @@ pgss_store(const char *query, uint64 queryId,\n query = CleanQuerytext(qu... |
[
{
"msg_contents": "Hi all,\n(Fujii-san and David in CC.)\n\nFujii-san has reported on Twitter that we had better add the TLI\nnumber to what pg_waldump --save-fullpage generates for the file names\nof the blocks, as it could be possible that we overwrite some blocks.\nThis information can be added thanks to ws_... |
[
{
"msg_contents": "Background:\n\nThe idea with 40af10b57 (Use Generation memory contexts to store\ntuples in sorts) was to reduce the memory wastage in tuplesort.c\ncaused by aset.c's power-of-2 rounding up behaviour and allow more\ntuples to be stored per work_mem in tuplesort.c\n\nLater, in (v16's) c6e0fe1f2... |
[
{
"msg_contents": "Hi,\n\nIn an off-list chat, Robert suggested that it might be a good idea to\nlook more closely into $subject, especially in the context of the\nproject of moving the locking of child tables / partitions to the\nExecInitNode() phase when executing cached generic plans [1].\n\nRobert's point i... |
[
{
"msg_contents": "Hi,\r\n\r\nPlease see the attached draft of the PostgreSQL 16 Beta 2 release \r\nannouncement.\r\n\r\nI used the open items list[1] to build the draft. If there are any \r\nnotable please omissions, please let me know.\r\n\r\nPlease leave all feedback by June 29, 0:00 AoE.\r\n\r\nThanks,\r\n\... |
[
{
"msg_contents": "This is a patch which implements an issue discussed in bug #17946[0]. It\ndoesn't fix the overarching issue of the bug, but merely a consistency\nissue which was found while analyzing code by Heikki. I had originally\nsubmitted the patch within that thread, but for visibility and the\npurpose... |
[
{
"msg_contents": "Hi,\n\n>I finished writing the code patch for transformation \"Or\" expressions to\n>\"Any\" expressions. I didn't see any problems in regression tests, even\n>when I changed the constant at which the minimum or expression is\n>replaced by any at 0. I ran my patch on sqlancer and so far the c... |
[
{
"msg_contents": "Hi,\n\nThis discussion started at https://postgr.es/m/20230627212423.p56zxuqeh5kyatqg@awork3.anarazel.de\nbut isn't really related to the bug.\n\n\nOn 2023-06-27 17:44:57 -0400, Tom Lane wrote:\n> Andres Freund <andres@anarazel.de> writes:\n> > That's not going to help you / the reporter, but... |
[
{
"msg_contents": "Hi, hackers\n\nThere has $subject that introduced by commit 6b4d23feef6. When we reset the entries\nif all parameters are avaiable, non-top-level entries removed first, then top-level\nentries.\n\n\n\n\n-- \nRegrads,\nJapin Li.",
"msg_date": "Wed, 28 Jun 2023 10:52:50 +0800",
"msg_fr... |
[
{
"msg_contents": "While looking at something unrelated, I noticed that the vacuumdb docs\nmention the following:\n\n\tvacuumdb might need to connect several times to the PostgreSQL server,\n\tasking for a password each time.\n\nIIUC this has been fixed since 83dec5a from 2015 (which was superceded by\nff402ae)... |
[
{
"msg_contents": "Dear Postgres Hackers,\n\nI hope this email finds you well. I am currently facing an issue while\nperforming an upgrade using the pg_upgrade utility with the --link option.\nI was under the impression that the --link option would create hard links\nbetween the old and new cluster's data files... |
[
{
"msg_contents": "This email has no patch yet -- it's more of a placeholder to gather some\nissues into one place. During previous work on replacing vacuum's bsearch'd\narray for TID storage with a radix tree, Andres suggested [1] that the hash\ntable in tidbitmap.c should also be replaced. This will hopefully... |
[
{
"msg_contents": "A quick scan of the archives doesn't turn up anyone who has volunteered in\nadvance to run the upcoming commitfest. Is anyone keen at trying their hand at\nthis very important community work? The July CF is good for anyone doing this\nfor the first time IMHO as it's usually less stressful t... |
[
{
"msg_contents": "Hi,\n\n\nMini repo\n\ncreate table t1(c1 int, c2 int);\nCREATE TABLE\ncreate table t2(c1 int, c2 int);\nCREATE TABLE\nexplain with cte1 as (insert into t2 values (1, 2) returning *) select * from cte1 join t1 using(c1);\n QUERY PLAN\n-----------------------------------------------------------... |
[
{
"msg_contents": "Hi,\n\nThis is a WIP patch to add WAL write and fsync stats to pg_stat_io\nview. There is a track_io_timing variable to control pg_stat_io\ntimings and a track_wal_io_timing variable to control WAL timings. I\ncouldn't decide on which logic to enable WAL timings on pg_stat_io.\nFor now, both ... |
[
{
"msg_contents": "Here are a few patches related to attstattarget:\n\n- 0001: Change type of pg_statistic_ext.stxstattarget, to match \nattstattarget. Maybe this should go into PG16, for consistency?\n\n- 0002: Add macro for maximum statistics target, instead of hardcoding \nit everywhere.\n\n- 0003: Take pg_... |
[
{
"msg_contents": "The MergeAttributes() and related code in and around tablecmds.c is huge \nand ancient, with many things bolted on over time, and difficult to deal \nwith. I took some time to make careful incremental updates and \nrefactorings to make the code easier to follow, more compact, and more \nmode... |
[
{
"msg_contents": "This patch adds a few examples to demonstrate the following:\n\n* The existence of the ctid column on every table\n* The utility of ctds in self joins\n* A practical usage of SKIP LOCKED\n\nThe reasoning for this is a bit long, but if you're interested, keep\nreading.\n\nIn the past, there ha... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.