threads listlengths 1 2.99k |
|---|
[
{
"msg_contents": "Hi,\n\nwe have txid_current(), which returns an int8. But there's no convenient\nway to convert that to type 'xid'. Which is fairly inconvenient, given\nthat we expose xids in various places.\n\nMy current need for this was just a regression test to make sure that\nsystem columns (xmin/xmax i... |
[
{
"msg_contents": "Hi folks\n\nI recently tracked down a race in shutdown of logical walsenders that can\ncause PostgreSQL shutdown to hang for wal_sender_timeout/2 before it\ncontinues to a normal shutdown. With a long timeout that can be quite\ndisruptive.\n\nTL;DR: The logical walsender may be signalled to s... |
[
{
"msg_contents": "Hi,\n\nInitdb fails when following path is provided as input:\ndatasadfasfdsafddsdatasadfasfdsafddsdatasadfasfdsafddsdatasadfasfdsafddsdatasadfasfdsafddsdatasadfasfdsafddsdatasadfasfdsafddsdatasadfasfdsafddsdatasadfasfdsafddsdatasadfasfdsafddsdatasadfasfdsafddsdatasadfasfdsafdds/datasadfasfds... |
[
{
"msg_contents": "Hi folks,\n\nI’ve run into a planning conundrum with my query rewriting extension for MVs when attempting to rewrite a RECURSIVE CTE.\n\nRECURSIVE CTEs are expensive — and presumably tricky to optimise — and so a good use case for query rewrite against an MV; all the more so if Yugo’s Increme... |
[
{
"msg_contents": "We've discussed this internally many times, but today finally decided\nto write up a doc patch.\n\nAutovacuum holds a SHARE UPDATE EXCLUSIVE lock, but other processes\ncan cancel autovacuum if blocked by that lock unless the autovacuum is\nto prevent wraparound.This can result in very surpris... |
[
{
"msg_contents": "Hello,\r\n\r\nI am just starting to get my feet wet with PostgreSQL development and am starting to understand the source, so please be kind 😊. I am working on the REL_11_4 tag.\r\n\r\nWhen CachedPlanSource instances are created the field query_string is filled with pstrdup(query_string) in C... |
[
{
"msg_contents": "Hello.\n\nWhile looking [1], I noticed that NOTICE messages of the next\ncommand is processed before PQgetResult returns. Clients can\nreceive such spurious NOTICE messages.\n\nLooking pqParseInput3, its main loop seems considered to exit\nafter complete messages is processed. (As I read.)\n\... |
[
{
"msg_contents": "Hi,\n\nI have noticed in some cases the warning messages appear twice, one such\ninstance is given below:\npostgres=# begin;\nBEGIN\npostgres=# prepare transaction 't1';\nPREPARE TRANSACTION\npostgres=# rollback;\n\n*WARNING: there is no transaction in progressWARNING: there is no\ntransact... |
[
{
"msg_contents": "Hello.\n\nWhile looking [1], I noticed that pg_walfile_name_offset behaves\nsomewhat oddly at segment boundary.\n\nselect * from (values ('0/16ffffff'), ('0/17000000'), ('0/17000001')) as t(lsn), lateral pg_walfile_name_offset(lsn::pg_lsn);\n lsn | file_name | file_offse... |
[
{
"msg_contents": "Hi All,\n\nI'm able to insert data into a table column marked as GENERATED ALWAYS\nusing COPY command however, it fails with INSERT command. Isn't that a\nbug with COPY command?\n\nHere is the test-case for more clarity.\n\npostgres=# create table tab_always (i int generated always as identi... |
[
{
"msg_contents": "Hello devs,\n\nAs pointed out by Kyotaro Horiguchi in\n\nhttps://www.postgresql.org/message-id/20190726.131704.86173346.horikyota.ntt@gmail.com\n\nFETCH_COUNT does not work with combined queries, and probably has never \nworked since 2006.\n\nWhat seems to happen is that ExecQueryUsingCursor ... |
[
{
"msg_contents": "Hi,\n\nWhen specifying a config a PGC_POSTMASTER variable on the commandline\n(i.e. -c something=other) the config processing blurts a wrong warning\nabout not being able to change that value. E.g. when specifying\nshared_buffers via -c, I get:\n\n2019-07-26 16:28:04.795 PDT [14464][] LOG: 0... |
[
{
"msg_contents": "Since we have three or four different NOTIFY improvement proposals\nfloating around in the current CF, I got a bit distressed at the lack\nof test coverage for that functionality. While the code coverage\nreport makes it look like commands/async.c isn't so badly covered,\nthat's all coming f... |
[
{
"msg_contents": "Hello,\n\nI just implemented a small change that adds another column \"mem_usage\" to the system view \"pg_prepared_statements\". It returns the memory usage total of CachedPlanSource.context, CachedPlanSource.query_content and if available CachedPlanSource.gplan.context.\n\nLooks like this:\... |
[
{
"msg_contents": "Hi,\n\nThe discussion in [1]\nagain reminded me how much I dislike that we currently issue database\nqueries in tap tests by forking psql and writing/reading from it's\nstdin/stdout.\n\nThat's quite cumbersome to write, and adds a good number of additional\nfailure scenarios to worry about. F... |
[
{
"msg_contents": "Hi,\n\nI noticed that after\n\ncommit 8255c7a5eeba8f1a38b7a431c04909bde4f5e67d\nAuthor: Tom Lane <tgl@sss.pgh.pa.us>\nDate: 2019-05-22 13:04:48 -0400\n\n Phase 2 pgindent run for v12.\n \n Switch to 2.1 version of pg_bsd_indent. This formats\n multiline function declarations \"... |
[
{
"msg_contents": "Hello hackers,\n\nPlease consider fixing the next set of typos and inconsistencies in the\ntree:\n8.1. LABORT -> LIKE_ABORT\n8.2. LagTrackerWriter -> LagTrackerWrite\n8.3. lag_with_offset_and_default, * ->\nwindow_lag_with_offset_and_default, window_* (in windowfuncs.c)\n8.4. language-name ->... |
[
{
"msg_contents": "Hello Andres,\n\nhow do you want to generalize it? Are you thinking about a view solely for the display of the memory usage of different objects? Like functions or views (that also have a plan associated with it, when I think about it)? While being interesting I still believe monitoring the m... |
[
{
"msg_contents": "Hi,\n\nI could not locate the caller of ParsePrepareRecord function in twophase.c.\nAny idea how it gets called?\nor\nIs it a dead function?\n\nRegards,\nVignesh\nEnterpriseDB: http://www.enterprisedb.com\n\nHi,I could not locate the caller of ParsePrepareRecord function in twophase.c.Any ide... |
[
{
"msg_contents": "Hi!\n\nDuring my work on bringing jsonpath patchset to commit, I was always\nkeeping in mind that we need to make jsonb_path_*() functions\nimmutable. Having these functions immutable, users can build\nexpression indexes over them. Naturally, in majority of cases one\ndoesn't need to index ... |
[
{
"msg_contents": "Hello,\n\n\nI attached one example of a partitioned table with multi column partition key. I also attached the output.\n\nDisabling the hash_join is not really necessary, it just shows the more drastic result in the case of low work_mem.\n\n\nComparing the first and the second query I was sur... |
[
{
"msg_contents": "Hi all,\n\nWhile reviewing some code around pg_lsn_in() I came across a couple of\n(potential?) issues:\n\n1.\nCommit 21f428eb moves lsn conversion functionality from pg_lsn_in() to a new\nfunction pg_lsn_in_internal(). It takes two parameters the lsn string and a\npointer to a boolean (*have... |
[
{
"msg_contents": "Hi,\n\nIn contrib/pgcrypto/pgp.c we have a struct member int_name in digest_info which\nisn’t used, and seems to have never been used (a potential copy/pasteo from the\ncipher_info struct?). Is there a reason for keeping this, or can it be removed\nas per the attached?\n\ncheers ./daniel",
... |
[
{
"msg_contents": "Hi,\n\nI've occasionally wished for a typesafe version of pg_printf() and other\nvarargs functions. The compiler warnings are nice, but also far from\ncomplete.\n\nHere's a somewhat crazy hack/prototype for how printf could get actual\nargument types. I'm far from certain it's worth pursuing... |
[
{
"msg_contents": "Logs are important to diagnose problems or monitor operations, but logs\ncan contain sensitive information which is often unnecessary for these\npurposes. Redacting the sensitive information would enable easier\naccess and simpler integration with analysis tools without compromising\nthe sens... |
[
{
"msg_contents": "Hi,\n\n\nI wrote a patch for adding CORRESPONDING/CORRESPONDING BY to set operation.\nIt is a task in the todo list. This is how the patch works:\n\n\nI modified transformSetOperationStmt() to get an intersection target list\nwhich is the intersection of the target lists of the left clause an... |
[
{
"msg_contents": "Hello,\n\nWhen we add a new path using add_path(), it checks estimated cost and path-keys,\nthen it also removes dominated paths, if any.\nDo we have a reasonable way to retain these \"dominated\" paths? Once it\nis considered\nlesser paths at a level, however, it may have a combined cheaper ... |
[
{
"msg_contents": "Hi,\n\nI noticed that there are many header files being\nincluded which need not be included.\nI have tried this in a few files and found the\ncompilation and regression to be working.\nI have attached the patch for the files that\nI tried.\nI tried this in CentOS, I did not find the header\n... |
[
{
"msg_contents": "Current Postgres implementation of temporary table causes number of \nproblems:\n\n1. Catalog bloating: if client creates and deletes too many temporary \ntables, then autovacuum get stuck on catalog.\n2. Parallel queries: right now usage of temporary tables in query \ndisables parallel plan.... |
[
{
"msg_contents": "Hi Tom,\n\nb654714 has reworked the way we handle removal of CLRF for several\ncode paths, and has repeated the same code patterns to do that in 8\ndifferent places. Could it make sense to refactor things as per the\nattached with a new routine in common/string.c?\n\nThanks,\n--\nMichael",
... |
[
{
"msg_contents": "Hi all,\n\n7cce1593 has introduced a new routine makeIndexInfo to create\nIndexInfo nodes. It happens that we can do a bit more refactoring as\nper the attached, as BuildIndexInfo can make use of this routine,\nremoving some duplication on the way (filling in IndexInfo was still\nduplicated ... |
[
{
"msg_contents": "Hi,\n\nIn the undo system, we use full-transaction-id for transactions. For\nrollback of prepared transactions, we were planning to use\nFullTransactionId by combining TransactionId and epoch, but as\nsuggested by multiple people in that email chain [1][2], the better\nidea is to store Full-... |
[
{
"msg_contents": "Hi,\n\nAttached fixes some typos for \"serialise\" => \"serialize\" and \"materialise\"\n=> \"materialize\".\n\nRegards,\n-- Sehrope Sarkuni\nFounder & CEO | JackDB, Inc. | https://www.jackdb.com/",
"msg_date": "Thu, 1 Aug 2019 08:24:17 -0400",
"msg_from": "Sehrope Sarkuni <sehrope@ja... |
[
{
"msg_contents": "The following bug has been logged on the website:\n\nBug reference: 15938\nLogged by: Alexander Kukushkin\nEmail address: cyberdemn@gmail.com\nPostgreSQL version: 10.9\nOperating system: Ubuntu 18.04.2 LTS\nDescription: \n\nOn one of our cluster one of the postgres... |
[
{
"msg_contents": "I pushed a commit that required a new pg_proc entry today. Had I not\nbeen involved with the work that became commit a6417078, I would\ndefinitely not have used an OID from the range reserved for devel\nsystem catalogs (8000 - 8999). As I understand it, this is now\nstandard practice.\n\nPerh... |
[
{
"msg_contents": "Hi,\n\nThe Release Management Team is pleased to announce that the release\ndate for PostgreSQL 12 Beta 3 is set to be 2019-08-08 (wrapping [1]\nthe release 2019-08-05), together with the next set of planned minor\nreleases. \n\nWe’re excited to make the third beta for this latest major relea... |
[
{
"msg_contents": "Hello,\n\nI currently have the problem that a simple prepared statement for a \nquery like\n\n select * from vw_report_invoice where id = $1\n\nresults in 33MB memory consumption on my side. It is a query that does \nabout >20 joins over partially wide tables, but only a very small subset... |
[
{
"msg_contents": "Hello,\n\nhttps://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=elver&dt=2019-07-24%2003%3A22%3A17\nhttps://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2019-08-02%2007%3A17%3A25\n\nI wondered if this might be like the recently fixed problem with slapd\nnot being ready to handle... |
[
{
"msg_contents": "Hi,\n\nThere have been five failures on three animals like this, over the\npast couple of months:\n\n step s6a7: LOCK TABLE a7; <waiting ...>\n step s7a8: LOCK TABLE a8; <waiting ...>\n step s8a1: LOCK TABLE a1; <waiting ...>\n-step s8a1: <... completed>\n step s7a8: <... completed>\n-error i... |
[
{
"msg_contents": "Hi hackers,\n\n\nWhile I was reviewing some code in another patch, I stumbled upon a possible optimization in the btree index code in nbtsearch.c for queries using 'LIMIT 1'. I have written a small patch that implements this optimization, but I'd like some feedback on the design of the patch,... |
[
{
"msg_contents": "Hoi hackers,\n\nHere is a reworked version of the previous patches.\n\nThe original three patches have been collapsed into one as given the\nchanges discussed it didn't make sense to keep them separate. There\nare now two patches (the third is just to help with testing):\n\nPatch 1: Tracks th... |
[
{
"msg_contents": "See\nhttps://git.postgresql.org/pg/commitdiff/082c9f5f761ced18a6f014f2638096f6a8228164\n\nPlease send comments/corrections before Sunday.\n\n\t\t\tregards, tom lane\n\n\n",
"msg_date": "Fri, 02 Aug 2019 16:21:07 -0400",
"msg_from": "Tom Lane <tgl@sss.pgh.pa.us>",
"msg_from_op": tr... |
[
{
"msg_contents": "Hi, \n\nI have found a bug in jsonb_plperl extension. A possible fix is proposed below.\n\njsonb_perl is the contrib module, which defines TRANSFORM functions for jsonb data type and PL/Perl procedural language.\n\nThe bug can be reproduced as follows:\n\nCREATE EXTENSION plperl;\nCREATE EXTE... |
[
{
"msg_contents": "Hello,\n\nWhile examining the reasons for excessive memory usage in prepared \nstatements I noticed that RTE_JOIN-kind RTEs contain a bunch of \ncolumnNames and joinaliasvars, that are irrelevant after the Query after \nhas been rewritten. I have some queries that join about 20 tables and \ns... |
[
{
"msg_contents": "Improve pruning of a default partition\n\nWhen querying a partitioned table containing a default partition, we\nwere wrongly deciding to include it in the scan too early in the\nprocess, failing to exclude it in some cases. If we reinterpret the\nPruneStepResult.scan_default flag slightly, w... |
[
{
"msg_contents": "Hello hackers,\n\nPlease consider fixing the next truss of typos and inconsistencies in\nthe tree:\n\n9.1. NAMESPACE_SQLXML -> remove (not used since the introduction in\n355e05ab)\n9.2. NBXLOG_H -> NBTXLOG_H\n9.3. NEWPAGE -> XLOG_FPI (orphaned since 54685338)\n9.4. newXlogId, newXlogSeg -> n... |
[
{
"msg_contents": "Hi all,\n\nI have noticed today that the two functions in $subject are part of\nlibpq and remain around undocumented since they are around (see\n6ef5846 and 2b84cbb). Isn't it past time to get rid of them? We have\nPQprint as well, which was used in the past by psql but not today,\nstill th... |
[
{
"msg_contents": "Hi ,\n\nWhile testing SSL version 1.1.1c , I only enabled TLSv1.2 and rest \nincluding TLSv1.3 has been disabled , like this -\n\npostgres=# show ssl_ciphers ;\n ssl_ciphers\n----------------------------------------------\n TLSv1.2:!aNULL:!SSLv2:!SSLv3:!TLSv1:!TLSv1.3\n\nTo ... |
[
{
"msg_contents": "Hi,\n\nSorry if this report is duplicate but there is no column relhasoids in\npg_catalog.pg_class required by the underlying query of the \\d meta\ncommand of psql.\n\n\n",
"msg_date": "Mon, 5 Aug 2019 14:38:40 +0300",
"msg_from": "Dmitry Igrishin <dmitigr@gmail.com>",
"msg_from_... |
[
{
"msg_contents": "-hackers,\n\nI went through and made some readability and modernization of the \nintro.sgml today. Patch attached.\n\nJD\n\n-- \nCommand Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc\nPostgres centered full stack support, consulting and development.\nAdvocate: @amplifypostgres... |
[
{
"msg_contents": "I got frustrated just now because this:\n\nhttps://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2019-08-05%2021%3A18%3A23\n\nis essentially undebuggable, thanks to the buildfarm's failure to\ncapture any error output from slapd. That's not the buildfarm\nscript's fault: it's will... |
[
{
"msg_contents": "postgres=# create table t (a int, b int);\nCREATE TABLE\npostgres=# create index m on t(a);\nCREATE INDEX\npostgres=# create index m2 on t(a);\nCREATE INDEX\npostgres=# \\d t\n Table \"demo.t\"\n Column | Type | Collation | Nullable | Default\n--------+---------+-----------... |
[
{
"msg_contents": "Hi,\n\nAttached patch for:\n\ns/incompable/incompatible/g\n\nThanks,\nAmit",
"msg_date": "Tue, 6 Aug 2019 17:34:06 +0900",
"msg_from": "Amit Langote <amitlangote09@gmail.com>",
"msg_from_op": true,
"msg_subject": "Fix a typo in add_partial_path"
},
{
"msg_contents": "O... |
[
{
"msg_contents": "I propose to apply the attached patch (to master) to update the DocBook\nversion to 4.5 (from 4.2). This basically just gets us off some random\nintermediate minor version to the latest within that major version.\n\nMost packagings put all 4.* versions into one package, so you probably\ndon'... |
[
{
"msg_contents": "I'm getting the below, and am unaware of how to fix it....\n\n11.4 on FreeBSD 12.\n\n\n\nler=# reindex (verbose) table dns_query ;\nINFO: index \"dns_query_pkey\" was reindexed\nDETAIL: CPU: user: 114.29 s, system: 207.94 s, elapsed: 698.87 s\nERROR: index \"pg_toast_17760_index\" contains... |
[
{
"msg_contents": "While looking at the pending patch for faster GIN index searches\non no-key queries, I was motivated to improve contrib/intarray's\nregression test to exercise the GIN_SEARCH_MODE_ALL case, because\nit didn't. And then I thought well, let's try to bring the code\ncoverage of _int_gin.c up to... |
[
{
"msg_contents": "Hi,\n\nThe attached self-documented patch fixes build on Windows in case when\npath to Python has embedded spaces.",
"msg_date": "Tue, 6 Aug 2019 22:50:14 +0300",
"msg_from": "Dmitry Igrishin <dmitigr@gmail.com>",
"msg_from_op": true,
"msg_subject": "Small patch to fix build o... |
[
{
"msg_contents": "Given the discussion starting at\nhttps://postgr.es/m/CAFjFpRdBiQjZm8sG9+s0x8Re-afHds6MFLgGuw0wVUNLGrVOQg@mail.gmail.com\nwe don't have default-partition support with the hash partitioning\nscheme. That seems a reasonable outcome, but I think we should have a\ncomment about it (I had to sear... |
[
{
"msg_contents": "Hello, here's a pretty trivial cleanup.\n\nCurrently, you have to pass the errmsg text to convert_tuples_by_name\nand convert_tuples_by_position that's going to be raised if the tuple\ndescriptors don't match. In the latter's case that makes sense, as each\ncase is pretty specific and tailor... |
[
{
"msg_contents": "Hi\n\nI should to use a cache accessed via fn_extra. There will be stored data\nabout function parameters (types). If I understand correctly, these data\nshould be stable in query, and then recheck is not necessary. Is it true?\n\nRegards\n\nPavel\n\nHiI should to use a cache accessed via fn_... |
[
{
"msg_contents": "The pool_passwd option [1] is specified relative to config file. But for\ngreater flexibility absolute path should be accepted as well.\n\nIf pool_passwd option starts with /, let's treat it as absolute path.\nOtherwise, it is treated as relative path.\n\nPatch attached. Original author - Der... |
[
{
"msg_contents": "Hi hackers,\n\nI wonder if there is some particular reason for not handling \nT_RestrictInfo node tag in expression_tree_walker?\nThere are many data structure in Postgres which contains lists of \nRestrictInfo or expression with RestrictInfo as parameter (for example \norclause in RestrictIn... |
[
{
"msg_contents": "Hello,\n\nThe word \"rewinded\" appears in our manual and in a comment. That\nsounds strange to my ears. Isn't it a mistake? Oxford lists the form\nas \"poetic\" and \"rare\", and then says it was used by one specific\nVictorian poet. Perhaps I'll send them a pull request: it's now G. M.\... |
[
{
"msg_contents": "Hi!\n\nI was playing around with JSON path quite a bit and might have found one case where the current implementation doesn’t follow the standard.\n\nThe functionality in question are the comparison operators except ==. They use the database default collation rather then the standard-mandated... |
[
{
"msg_contents": "The list of tests in src/test/isolation/isolation_schedule has grown \nover the years. Originally, they were all related to Serializable \nSnapshot Isolation, but there are different kinds of concurrency tests \nthere now. More tests is good, but the schedule file has grown into a \nbig inscr... |
[
{
"msg_contents": "Small patch to simplify some no longer necessary complicated code, using\nvarargs macros.\n\n-- \nPeter Eisentraut http://www.2ndQuadrant.com/\nPostgreSQL Development, 24x7 Support, Remote DBA, Training & Services",
"msg_date": "Wed, 7 Aug 2019 14:35:54 +0200",
"msg_from"... |
[
{
"msg_contents": "Hi all,\n\nWhile browsing the buildfarm failures, I have found this problem on\nanole for the test temp:\nhttps://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=anole&dt=2019-08-07%2006%3A39%3A35\n select relname from pg_class where relname like 'temp_parted_oncommit_test%';\n r... |
[
{
"msg_contents": "It works!\n\n(apparently as of Windows 10 version 1803)\n\nHere are some patches to get a discussion rolling.\n\nBasically, it just works, but you need to define your own struct\nsockaddr_un. (This is what configure currently uses as a proxy for\nHAVE_UNIX_SOCKETS, so (a) that needs a bit of... |
[
{
"msg_contents": "Over in [1] we realized that it would be a good idea to remove the <@\noperator from contrib/intarray's GiST opclasses. Unfortunately, doing\nthat isn't a simple matter of generating an extension update script\ncontaining ALTER OPERATOR FAMILY DROP OPERATOR, because that operator\nis marked ... |
[
{
"msg_contents": "A daily report crashed repeatedly this morning running pg11.4.\nI compiled 11.5 and reproduced it there, too, so I'm including backtrace with\n-O0.\n\nI'm trying to dig further into it, but it seems to be crashing under load, but\nnot when I try to narrow down to a single report, which seem t... |
[
{
"msg_contents": "I'm looking at https://www.postgresql.org/docs/current/sql-analyze.html,\nwhere it says “Without a table_and_columns list, ANALYZE processes every\ntable and materialized view in the current database that the current user\nhas permission to analyze.”.\n\nI don’t believe there is a separate “a... |
[
{
"msg_contents": "Hello all,\n\nPlease find attached a trivial patch making a few arrays const (in addition\nto the data they point to).",
"msg_date": "Thu, 8 Aug 2019 09:46:06 +0300",
"msg_from": "Mark G <markg735@gmail.com>",
"msg_from_op": true,
"msg_subject": "Small const correctness patch"... |
[
{
"msg_contents": "Hi,\n\nIn RelationBuildPartitionDesc(), a memory space that use to gather\npartitioning\nbound info wasn't free at the end. This might not a problem because this\nallocated memory will eventually be recovered when the top-level context is\nfreed, but the case when a partitioned table having ... |
[
{
"msg_contents": "I am Yonathan Misgan from Ethiopia, want to add some functionalities on PostgreSQL to support Ethiopian locales. I want your advice where I start to hack the PostgresSQL source code. I have attached some synopsis about the existing problems of PostgresSQL related with Ethiopian locale special... |
[
{
"msg_contents": "Hi, hackers\n\n\"The local variables that do not have the volatile type and have been changed\nbetween the setjmp() invocation and longjmp() call are indeterminate\". This is\nwhat the POSIX (and C standard for setjmp) says.\n\nThat's fine actually, but if we put the PG_TRY()/CATCH() in a loo... |
[
{
"msg_contents": "A long time ago, we changed LC_COLLATE and LC_CTYPE from cluster-wide to\nper-database (61d967498802ab86d8897cb3c61740d7e9d712f6). There is some\nleftover code from that in initdb.c and backend/main/main.c to pass\nthese environment variables around in the expectations that the backend\nwill... |
[
{
"msg_contents": "Libpq doesn't have a way to control which password protocols are used.\nFor example, the client might expect the server to be using SCRAM, but\nit actually ends up using plain password authentication instead.\n\nThis patch adds:\n\n password_protocol = {plaintext|md5|scram-sha-256|scram-sha-... |
[
{
"msg_contents": "On Fri, Sep 9, 2016 at 6:14 AM Heikki Linnakangas <hlinnaka@iki.fi> wrote:\n> 1. SortTuple.tupindex is not used when the sort fits in memory. If we\n> also got rid of the isnull1 flag, we could shrink SortTuple from 24\n> bytes to 16 bytes (on 64-bit systems). That would allow you to pack mor... |
[
{
"msg_contents": "Hi all,\n\nFollowing a recent bug report \n(<https://www.postgresql.org/message-id/20190725015448.e5a3rwa22kpnzfe3%40alap3.anarazel.de>) \nit was suggested that that I submit a feature request for the ability \nto test whether an (insert / on conflict update) \"upsert\" resulted in \nan inser... |
[
{
"msg_contents": "Hello hackers,\n\nPlease consider fixing the next heap of typos and inconsistencies in the\ntree:\n\n10.1. query_txt -> query text\n10.2. quote_object_names -> quote_object_name\n10.3. ragetypes_typanalyze.c -> rangetypes_typanalyze.c\n10.4. RAISE_EXCEPTION -> ERRCODE_RAISE_EXCEPTION\n10.5. r... |
[
{
"msg_contents": "Hi all,\nI hope this is the right list for my question, if not, please let me know\nto which list I should send the question.\n\nI'd like to know whether there is any way to control the order of inherited\ncolumns?\n\nThis is purely an issue of syntactic sugar for me. I'd like to be able to\n... |
[
{
"msg_contents": "Hello,\n\nPostgreSQL optimizer right now considers join pairs on only\nnon-partition - non-partition or\npartition-leaf - partition-leaf relations. On the other hands, it is\nharmless and makes sense to\nconsider a join pair on non-partition - partition-leaf.\n\nSee the example below. ptable ... |
[
{
"msg_contents": "Hi hackers!\n\nCurrently, if we check indexes on standby we often get\n\nman-psbpshn0skhsxynd/xiva_xtable_testing_01 R # select bt_index_check('xiva_loadtest.pk_uid');\nERROR: 58P01: could not open file \"base/16453/125407\": No such file or directory\n\nI think that we should print warning ... |
[
{
"msg_contents": "Hi,\n\nI got following log messages when measured the heap truncating\nduration in a vacuum.\n\n=====================================================\nINFO: \"dst\": suspending truncate due to conflicting lock request\nINFO: \"dst\": truncated 550073 to 101472 pages\nDETAIL: CPU: user: 0.3... |
[
{
"msg_contents": "Hi all,\n\nI'd like to get some feedback on whether or not implementing a DNS SRV feature\nfor connecting to PostgreSQL would be desirable/useful.\n\nThe main use case is to have a DNS SRV record that lists all the possible\nprimaries of a given replicated PostgreSQL cluster. With auto failov... |
[
{
"msg_contents": "I am working on an extension that uses background workers, and interested\nin adding code for it to auto-restart after a crash or server restart\n(similar to as-coded in worker_spi).\n\nBut I'm also interested in being able to configure bgw_restart_time using a\nGUC without having to restart ... |
[
{
"msg_contents": "Hello pgdevs,\n\nThe attached patch improves pgbench variable management as discussed in:\n\nhttps://www.postgresql.org/message-id/flat/alpine.DEB.2.21.1904081752210.5867@lancre\n\nAs discussed there as well, the overall effect is small compared to libpq \n& system costs when pgbench is talki... |
[
{
"msg_contents": "The easiest way to see this is to BEGIN READ ONLY & then attempt an insert. Execute either of COMMIT AND CHAIN or ROLLBACK AND CHAIN & attempt the insert a second time\n\nThis seems incorrect. The documentation should at least point out this behavior if it's intended\n\n\n\n\n\n\n\n\n\nThe ea... |
[
{
"msg_contents": "Hi,\n\nHere are three strange recent failures in the \"rules\" test:\n\nhttps://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=blenny&dt=2019-08-13%2022:19:27\nhttps://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=alewife&dt=2019-07-27%2009:39:05\nhttps://buildfarm.postgresql.org/cgi-bin/s... |
[
{
"msg_contents": "I'm confused by how the code uses the term \"verifier\" in relation to SCRAM.\n\nISTM that the code uses the term as meaning whatever is or would be\nstored in pg_auth.rolpassword.\n\nI don't see this usage supported in the RFCs. In RFC 5802,\n\n verifier = \"v=\" base64\n ... |
[
{
"msg_contents": "I want to use valgrind to detect memory leak issue. Then I run into 2\nproblems I want to confirm them here.\n\nQ1: can I use 'leak-check=yes' to detect memory leak issue?\n1. In https://wiki.postgresql.org/wiki/Valgrind, the wiki indicates to\nuse '--leak-check=no'\n2. in https://gith... |
[
{
"msg_contents": "This kind of output is usually not helpful:\n\nTRAP: BadArgument(\"((context) != ((void *)0) && (((((const\nNode*)((context)))->type) == T_AllocSetContext) || ((((const\nNode*)((context)))->type) == T_SlabContext) || ((((const\nNode*)((context)))->type) == T_GenerationContext)))\", File:\n\".... |
[
{
"msg_contents": "I notice that for a pg_amop object, getObjectDescription does this:\n\n /*------\n translator: %d is the operator strategy (a number), the\n first two %s's are data type names, the third %s is the\n description of the operat... |
[
{
"msg_contents": "Hello, I am trying to develop calendar extension for PostgreSQL but there is a difficulties on how to get day, month and year from PostgreSQL source code because when am read the PostgreSQL source code it uses DateADT as a data type and this DateADT returns the total numbers of day. So how c... |
[
{
"msg_contents": "Hi,\n\nWhile working on the PWJ patch [1], I noticed $SUBJECT. They seem to\nbe leftovers from the original partitionwise-join patch, perhaps.\nAttached is a patch for removing them.\n\nBest regards,\nEtsuro Fujita\n\n[1] https://www.postgresql.org/message-id/CAPmGK16wDqJiUof8+e4HuGmrAqqoFzb... |
[
{
"msg_contents": "This is an implementation of the idea I mentioned in [0].\n\nThe naming and description perhaps isn't ideal yet but it works in\nprinciple.\n\nThe idea is that if you connect over a Unix-domain socket and the local\n(effective) user is the same as the server's (effective) user, then\naccess s... |
[
{
"msg_contents": "Dear all,\n\nI was wondering if someone could help me understands what a union all\nactually does.\n\nFor my thesis I am using Apache Calcite to rewrite queries into using\nmaterialized views which I then give to a Postgres database.\nFor some queries, this means that they will be rewritten i... |
[
{
"msg_contents": "It seems that sometimes when DELETE cascades to referencing tables we fail\nto acquire locks on replica identity index.\n\nTo reproduce, set wal_level to logical, and run 1.sql.\n\nI can look into this, but I thought first I should send it here in case\nsomeone who is more familiar with these... |
[
{
"msg_contents": "Somebody ran into issues when generating large XML output (upwards of\n256 MB) and then sending via a connection with a different\nclient_encoding. This occurs because we pessimistically allocate 4x as\nmuch memory as the string needs, and we run into the 1GB palloc\nlimitation. ISTM we can... |
[
{
"msg_contents": "Everywhere I've worked I've seen people struggle with table bloat. It's\nhard to even measure how much of it you have or where, let alone actually\nfix it.\n\nIf you search online you'll find dozens of different queries estimating how\nmuch empty space are in your tables and indexes based on ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.