threads listlengths 1 2.99k |
|---|
[
{
"msg_contents": "Hi,\n\nI'm regularly using pg_stat_database view to analyze various aspects of\nbehavior of the cluster. The #1 issue I'm constantly running into is\nthat to get cluster-level view (across all the databases), the table\nneeds to be aggregated like this:\n\n SELECT\n SUM(blks_hit) bl... |
[
{
"msg_contents": "I've often wanted to know what the autovacuum worker was doing. The\nprocess title seems like the best place to get this information, but the\nprocess title tells me what database it is in, but not what table it is\nworking on.\n\nThe attached patch demonstrates the concept of what I want. ... |
[
{
"msg_contents": "If I create a database and install postgis as an extension, and then run\npg_dump I get this:\n\n[...]\nCREATE EXTENSION IF NOT EXISTS postgis WITH SCHEMA public;\n[...]\nCREATE RULE geometry_columns_delete AS ON DELETE TO geometry_columns DO\nINSTEAD NOTHING;\n[...]\n\nShouldn't that CREATE ... |
[
{
"msg_contents": "from the pg doc：\nhttp://www.postgresql.org/docs/devel/static/wal-reliability.html :On Linux,\nIDE drives can be queried using hdparm -I; write caching is enabled if\nthere is a * next to Write cache. hdparm -W 0 can be used to turn off write\ncaching. SCSI drives can be queried using\nsdparm... |
[
{
"msg_contents": "While reviewing the latest incarnation of the regex indexing patch,\nI noticed that make_trigrams() in contrib/pg_trgm/trgm_op.c is coded\nso that if USE_WIDE_UPPER_LOWER is not set, it ignores multibyte\ncharacter boundaries and just makes trigrams from 3-byte substrings.\nThis seems slightl... |
[
{
"msg_contents": "Get rid of USE_WIDE_UPPER_LOWER dependency in trigram construction.\n\ncontrib/pg_trgm's make_trigrams() was coded to ignore multibyte character\nboundaries and just make trigrams from bytes if USE_WIDE_UPPER_LOWER wasn't\ndefined. This is a bit odd, since there's no obvious reason why trigr... |
[
{
"msg_contents": "Hello,\n\nWhile going through the TODO items on the wiki I have come across the\nfollowing proposal:\n\nProvide a way to query the log collector subprocess to determine the\nname of the currently active log file\n\n Current log files when rotating?\n http://archives.postgresql.org/pgsql-gen... |
[
{
"msg_contents": "Hi,\n\nI'm learning how to use the \"background worker processes\" commited in\n9.3. The usage basics are quite nicely illustrated in the worker_spi\nextension (kudos to those who designed the feature / extension).\n\nI'm not quite sure how to pass data between the regular backend and a\nwork... |
[
{
"msg_contents": "Hello,\n\nWe have been trying to figure out possible solutions to the following\nproblem in streaming replication Consider following scenario:\n\nIf master receives commit command, it writes and flushes commit WAL records\nto the disk, It also writes and flushes data page related to this\ntra... |
[
{
"msg_contents": "Hello,\n\nWhile walking in the code I see the following code in\nsrc/backend/access/transam/xlogreader.c:177-191\n\nXLogRecord *\nXLogReadRecord(XLogReaderState *state, XLogRecPtr RecPtr, char **errormsg)\n{\n\tXLogRecord *record;\n\tXLogRecPtr\ttargetPagePtr;\n\tbool\t\trandAccess = false; ... |
[
{
"msg_contents": "Hi,\n\nDebian has been patching pg_regress for years because our default unix\nsocket directory is /var/run/postgresql, but that is not writable by\nthe build user at build time. This used to be a pretty ugly \"make-\npatch-make check-unpatch-make install\" patch dance, but now it is a\nprett... |
[
{
"msg_contents": "The materialized views patch adjusted ExplainOneQuery to take an\nadditional DestReceiver argument, but failed to add a matching\nargument to the definition of ExplainOneQuery_hook. This makes the\nhook unusable. The idea of this hook is that your hook function will\ndo something before and... |
[
{
"msg_contents": "The following bug has been logged on the website:\n\nBug reference: 8049\nLogged by: Teun Hoogendoorn\nEmail address: th@atsc.nl\nPostgreSQL version: 9.2.4\nOperating system: CentOS 6.3 final 64bit\nDescription: \n\nHi,\n\nI've got a strange problem with a query th... |
[
{
"msg_contents": "Buildfarm critters friarbird and jaguarundi have been failing for 11 \ndays, apparently due to the sql_drop event for event triggers feature. \nThese are both FBSD machines, but more importantly are both building \nwith -DCLOBBER_CACHE_ALWAYS.\n\nTom complained about it at the time, see \n<ht... |
[
{
"msg_contents": "Just today one of my systems experienced a kernel panic, and halted abruptly.\nRunning Linux 3.1.9, PostgreSQL 9.0.4 (Debian 9.0.4-1+b1, to be precise).\n\nThe system was moderately active, i.e. about one commit per minute.\nIt is not a large problem if the last few commits would be gone.\n\n... |
[
{
"msg_contents": "Hi all,\n\nI've just subscribed to this mailing list, so I thought it would be nice to\nintroduce myself.\nI'm Bert Desmet, and I currently live in Belgium.\nI work for Deloitte, where we are building a cloud BI platform. As a\ndatabase for the datawarehouses we use PostgreSQL since a few mon... |
[
{
"msg_contents": "About a month ago, I told Kevin Grittner in an off-list conversation\nthat I'd work on providing him with some statistics about lwlock\ncontention under SSI. I then ran a benchmark on a 16-core,\n64-hardware thread IBM server, testing read-only pgbench performance\nat scale factor 300 with 1... |
[
{
"msg_contents": "Just for fun, I implemented a toy background worker tonight using the\nnew bgworker framework. Generally, it went well, and I'm pleased with\nthe design of the new facility. However, I did notice one oddity. I\ninitialized the worker flags like this:\n\n worker.bgw_flags = BGWORKER_S... |
[
{
"msg_contents": "Hi,\n\nI'm wondering if this is a bug of PostgreSQL.\n\nPostgreSQL's show that replication_timeout parameter can \"Terminate replication connections that are inactive longer than the specified number of milliseconds\". But in my environment the sender process is hang up (in several tens of m... |
[
{
"msg_contents": "Hi all,\n\n I'd like to introduce myself to the dev community. I am Shuai Fan, a student from Dalian University of Technology, DLUT , for short, China. And I am interested in working with PostgreSQL project in GSOC2013.\n I'm interested in the idea \"Rewrite (add) pg_dump and pg_restore... |
[
{
"msg_contents": "If I'm reading the code right [1], this GUC does not actually *synchronize*\nthe scans, but instead just makes sure that a new scan starts from a block\nthat was reported by some other backend performing a scan on the same\nrelation.\n\nSince the backends scanning the relation may be processi... |
[
{
"msg_contents": "src/backend/catalog/dependency.c:213: EventTriggerSupportsObjectType(getObjectClass(thisobj)))\nsrc/backend/commands/event_trigger.c:1014: Assert(EventTriggerSupportsObjectType(getObjectClass(object)));\n\ngetObjectClass() returns type ObjectClass, but\nEventTriggerSupportsObje... |
[
{
"msg_contents": "I guess I'm a couple releases late to review the \"autovacuum truncate\nexclusive lock\" patch (a79ae0bc0d454b9f2c95a), but this patch did not only\naffect autovac, it affects manual vacuum as well (as did the original\nbehavior it is a modification of). So the compiler constants are misname... |
[
{
"msg_contents": "Hi,\n\nPlease find attached a patch to take 'make check' code-coverage of COLLATE\n(/src/backend/commands/collationcmds) from 0% to 96%.\n\nAny feedback is more than welcome. Also posting this to Commitfest-next.\n--\nRobins Tharakan\n\n\n-- \nSent via pgsql-hackers mailing list (pgsql-hacker... |
[
{
"msg_contents": "We are nearing April 15 --- are we nearing a time when we can close 9.3\ndevelopment and start focusing on the beta?\n\n-- \n Bruce Momjian <bruce@momjian.us> http://momjian.us\n EnterpriseDB http://enterprisedb.com\n\n + It's impossible for everything t... |
[
{
"msg_contents": "After patching to 9.2.4 I am noticing some mysterious behavior in my\nnightly vacuumdb cron job.\n\nI have been running vacuumdb -avz nightly for a while now, and have a\nscript that tells me the next day if all the tables in pg_stat_user_tables\nhave been vacuumed and analyzed in the last 24... |
[
{
"msg_contents": "I looked into the problem reported at\nhttp://www.postgresql.org/message-id/E1UPa3B-0004K0-PJ@wrigleys.postgresql.org\nwhich is that we're deriving a bogus plan for this query:\n\nSELECT * FROM\n(\n SELECT (COALESCE(h_n || '/', '') || l_n)::text AS fault\n FROM\n (\n\tSELECT _bug_header.h_... |
[
{
"msg_contents": "This blog entry displays the new 9.3 error fields, schema/table/constraint:\n\n\thttp://www.depesz.com/2013/03/07/waiting-for-9-3-provide-database-object-names-as-separate-fields-in-error-messages/\n\t\n\t$ INSERT INTO t (i) VALUES (1);\n\tpsql:z.sql:16: ERROR: 23505: duplicate key value vio... |
[
{
"msg_contents": "Hi hackers,\n\nMy name is Miguel Angel de Blas. I'm newbie and it's my first collaborationso I\nhope it's correct ;-)\n\nI created a function SPI_gettypmod:\n\nint32 SPI_gettypmod(TupleDesc tupdesc, int fnumber);\nReturn -1 when type not need type-specific data or error.\n\nref TODO:\n\nAd... |
[
{
"msg_contents": "Hello,\n\nThe current process of transferring data files from one cluster to another\nby using pg_dump and pg_restore is time consuming.\n\nThe proposed tool tries to make migration faster for tables and indices\nonly by copying their binary data files. This is like pg_upgrade but used\nfor m... |
[
{
"msg_contents": "Hi,\n\nWhile creating regression tests for EXPLAIN I am (somehow) unable to get\n(TIMING) option to work with EXPLAIN!\n\nI must be doing something stupid but all these options below just didn't\nwork. Could someone point me to the right direction?\n\nmpf2=# explain (TIMING) SELECT 1;\nERROR:... |
[
{
"msg_contents": "Programming language environment whose parser and interpreter are written\nwith plpgsql. Proof of concept prototype has been tested. An object\noriented programming language implemented with self-describing Entity\nAttribute Value model that stores objects and object metadata descriptions.\nT... |
[
{
"msg_contents": "While debugging an out-of-memory situation, I noticed that the relcache \nentry of each index consumes 2k of memory. From a memory dump:\n\n>...\n> pg_database_datname_index: 2048 total in 1 blocks; 712 free (0 chunks); 1336 used\n> pg_trigger_tgrelid_tgname_index: 2048 total in 1 blo... |
[
{
"msg_contents": "Could we generated sha256 files for the release tarballs, instead of the\nmd5 files that are currently generated? The packaging systems that I\nsurveyed that verify the checksum of the tarball (FreeBSD ports and the\nlike) don't use md5 anymore, so a sha256 file would be much more useful\nfo... |
[
{
"msg_contents": "COPY cannot be optimised correctly if we have before triggers or\nvolatile default expressions.\n\nThe multi-insert code detects those cases and falls back to the single\nrow mechanism in those cases.\n\nThere a common class of volatile functions that wouldn't cause\nproblems: any volatile fu... |
[
{
"msg_contents": "In current 9.3, I see:\n\n$ select p.proname, p.provolatile from pg_proc p join pg_namespace n on p.pronamespace = n.oid where n.nspname = 'pg_catalog' and p.proname ~ 'json';\n proname | provolatile \n---------------------------+-------------\n json_in | s... |
[
{
"msg_contents": "Hi guys.\nI created a type 'mytype' (an unsigned int) and created an operator class\nfor index.\nThen I created a table with a column of my type and isnerted 1000 entries.\nBut no matter how many entries I have in the table, it never uses the\nindex. It always does a seq scan.\n\nHere is the ... |
[
{
"msg_contents": "Hi,\nis there a way to clear the session state of sequence values fetched by \ncurrval(regclass)? \"DISCARD ALL\" doesn't seem to do it.\n\neg. (w/ pg 9.2.4)\ntest=# CREATE SEQUENCE foo_seq;\nCREATE SEQUENCE\ntest=# SELECT nextval('foo_seq');\n-[ RECORD 1 ]\nnextval | 1\n\ntest=# SELECT currv... |
[
{
"msg_contents": "I'm having trouble finding documentation about how to write event\ntriggers. The chapter in the documentation\n\nhttp://www.postgresql.org/docs/devel/static/event-triggers.html\n\nsays they can be written in C or supported PLs, but does not explain it\nany further. Is there any documentatio... |
[
{
"msg_contents": "Hi,\n\nHere's a new version of a small patch to psql I'm using locally.\n\nIt adds a command \\ns to psql which is a shortcut to set the\nSEARCH_PATH variable.\n\nI'd like to make a case for including this patch as it makes use of\nschemas/namespaces much easier. There was resistance to inclu... |
[
{
"msg_contents": "I propose the attached patch to change pg_test_fsync's output from\n\"microsecs\" to \"usecs\", which is the designation we use in other places.\nAlso remove parentheses, e.g. \n\n 1 * 16kB open_sync write 8012.933 ops/sec 125 usecs/op\n 2 * 8kB open_sync writes ... |
[
{
"msg_contents": "This code in bootstrap.c contains a sequence point violation (or\nwhatever that is really called):\n\n while ((tup = heap_getnext(scan, ForwardScanDirection)) != NULL)\n {\n (*app)->am_oid = HeapTupleGetOid(tup);\n memmove((char *) &(*app++)->am_typ,\n ... |
[
{
"msg_contents": "Hello,\n\nMany of the links in the TODO wiki page result in a \"page not found\" error.\nIs this page up-to-date?\nCan anything be inferred about the status of these items from the broken\nlink?\n\nThanks.\n\nhttp://wiki.postgresql.org/wiki/Todo\n\nHello,Many of the links in the TODO wiki pag... |
[
{
"msg_contents": "Hello dear -hackers,\n\nI'm maintaining pg_reorg/pg_repack, which you may know effectively\nallow online VACUUM FULL or CLUSTER. It works by installing logging\ntriggers to keep data up-to-date during the migration, creating a copy\nof the table, and eventually swapping the tables relfilenode... |
[
{
"msg_contents": "Hi all,\n\nThe attached patch fix a little typo on contrib/hstore/crc32.c comment.\n\nRegards,\n\n-- \nFabrízio de Royes Mello\nConsultoria/Coaching PostgreSQL\n>> Blog sobre TI: http://fabriziomello.blogspot.com\n>> Perfil Linkedin: http://br.linkedin.com/in/fabriziomello\n>> Twitter: http:/... |
[
{
"msg_contents": "I'm wondering how I can store word-level bigrams/trigrams in a tsvector\nthat I can query against. I was expecting the final query to match \"the\nair\" and return the one tuple to me.\n\nFor instance:\n\npostgres=# create table docs (a tsvector);\nCREATE TABLE\npostgres=# insert into docs (a... |
[
{
"msg_contents": "When archive_command fails three times, it prints this message into the\nlogs:\n\n\"transaction log file \\\"%s\\\" could not be archived: too many failures\"\n\nThis leaves it open what happens next. What will actually happen is\nthat it will usually try again after 60 seconds or so, but th... |
[
{
"msg_contents": "I just found out that if you use continuous archiving and online \nbackups, it's surprisingly difficult to restore a backup, without \nreplaying any more WAL than necessary.\n\nIf you don't set a recovery target, PostgreSQL will recover all the WAL \nit finds. You can set recovery target time... |
[
{
"msg_contents": "While trying out CURRENT OF with foreign table, ending up with error.\n\npostgres=# select version();\n version\n\n-----------------------------------------------------------------------------------------------------------------\n PostgreSQL... |
[
{
"msg_contents": "Hello All,\nI'm writing today to inquire about finding the exact point in the source\nwhere postgres writes to disk. I'm trying to implement some compression in\npostgres. The idea is to compress the data right when its written to disk,\nto reduce the amount of data written to disk, reducing ... |
[
{
"msg_contents": "Do we really want to generate just a warning for a checksum failure, and\nnot an error; see PageIsVerified().\n\n-- \n Bruce Momjian <bruce@momjian.us> http://momjian.us\n EnterpriseDB http://enterprisedb.com\n\n + It's impossible for everything to be t... |
[
{
"msg_contents": "Hi all,\n\nI have been writing pg extensions for a while but I just ran into a \nproblem that has me stumped.\n\nI have code for a SRF and it works fine on pg 9.2.2 on linux, but fails \nwith am error in the logfile.\n\nTRAP: FailedAssertion(\"!(context != CurrentMemoryContext)\", File: \n\"... |
[
{
"msg_contents": "I am not sure if Tom shared yet, but we are planning to package 9.3\nbeta1 on April 29, with a release on May 2. Those dates might change,\nbut that is the current plan. I have completed a draft 9.3 release\nnotes, which you can view here:\n\n\thttp://momjian.us/pgsql_docs/release-9-3.html\... |
[
{
"msg_contents": "A few years ago I wrote a roll-your-own foreign-data-wrapper system for\nPostgres because Postgres didn't have one at the time (some details\nhere<http://unubtainabol.blogspot.com/2013/04/daves-foreign-data-introuction.html>if\nanyone is interested). Now I'm being tasked to move it to Postgre... |
[
{
"msg_contents": "We never reached a consensus on the user interface of the new 'fast \npromotion'. We should settle that before beta. The thread died here:\n\nhttp://www.postgresql.org/message-id/CA+U5nMKmDD7hGCYzOo=iFM=eK5OPDXCEzmq79fgLWr0TJk=sXw@mail.gmail.com\n\nSimon said in that email that he's waiting f... |
[
{
"msg_contents": "Greetings,\n\nHello, my name is Michael Schuh and I am a PhD student in Computer Science\nat Montana State University. I have never participated in GSOC before, but\nI am very excited to propose a project to PostgreSQL that I feel would be a\ngreat follow-up to last year's project by Alexande... |
[
{
"msg_contents": "Hi,\n\nI have observed that following sequence is causing server crash.\n\nCREATE MATERIALIZED VIEW temp_class_mv AS\n SELECT * FROM pg_class\n WITH NO DATA;\n\nCREATE OR REPLACE FUNCTION test_refresh_mv()\nRETURNS int\nAS $$\nBEGIN\n REFRESH MATERIALIZED VIEW temp_class_mv;\n return 1;\nEN... |
[
{
"msg_contents": "Hi,\nWe are seeing some overall performance degradation in our application \n since we installed the security release. Other commits were also done \nat the same time in the application so we don't know yet if the \n degradation has any relationship with the security release.\n\n While we are... |
[
{
"msg_contents": "My first message has been banned for too many latters.\n\n> \nHi all\nThere is something wrong and ugly.\n\n1)\nIntel 32 core = 2*8 *2threads\n\nLinux avi-sql09 2.6.32-5-amd64 #1 SMP Sun May 6 04:00:17 UTC 2012 x86_64 GNU/Linux\n\nPostgreSQL 9.2.2 on x86_64-unknown-linux-gnu, compiled by gcc-... |
[
{
"msg_contents": "Noah Misch pointed out something interesting to me:\n\n/*\n * PQputCopyEnd - send EOF indication to the backend during COPY IN\n *\n * After calling this, use PQgetResult() to check command completion status.\n *\n * Returns 1 if successful, 0 if data could not be sent (only possible\n * in n... |
[
{
"msg_contents": "The function\n\nstatic char *\npath_encode(bool closed, int npts, Point *pt)\n\nis actually occasionally passed -1 as its first parameter to mean\nsomething like \"neither\" or \"don't print any delimiters\". That doesn't\nseem like good style. Maybe this should be split off into another bo... |
[
{
"msg_contents": "Starting a new thread to more narrowly address the topic.\n\nAttached is my reorganization of Ants's patch here:\n\nhttp://www.postgresql.org/message-id/CA\n+CSw_vinyf-w45i=M1m__MpJZY=e8S4Nt_KNnpEbtWjTOaSUA@mail.gmail.com\n\nMy changes:\n\n* wrest the core FNV algorithm from the specific conc... |
[
{
"msg_contents": "Hello,\n\nI was playing with pg_xlogdump in the HEAD and found a few issues.\n\n1. Tried compiling pg_xlogdump via PGXS mechanism and it fails with the\nfollowing error:\nmake: *** No rule to make target\n`/home/pavan.deolasee/work/pgsql/postgresql/install/lib/pgxs/src/makefiles/../../src/bac... |
[
{
"msg_contents": "Hi all,\n\nI noticed the need to simply stop a bgworker after its work is done but\nstill have it restart in unusual circumstances like a crash.\nObviously I can just have it enter a loop where it checks its latch and\nsuch, but that seems a bit pointless.\n\nWould it make sense to add an ext... |
[
{
"msg_contents": "psql currently collects the query result rows in memory before writing them\nto a file and can cause out of memory problems for large results in low\nmemory environments like ec2. I can't use COPY TO STDOUT or FETCH_COUNT\nsince I'm using Redshift and it doesn't support [writing to STDOUT](\n... |
[
{
"msg_contents": "Folks,\n\nWhile testing the upcoming FILTER clause for aggregates, Erik Rijkers\nuncovered a long-standing bug in $subject, namely that this case\nwasn't handled. Please find attached a patch by Andrew Gierth and\nmyself which fixes this issue and adds a regression test to ensure it\nremains... |
[
{
"msg_contents": "In our production environment, we separate each shard out into its own\nschema to give us flexibility in shard location. This leaves us with a\nlot of schemas hosted on a relatively smaller set of servers.\n\nWith so many schemas, database migrations started to take a long time\nto run across... |
[
{
"msg_contents": "Hi All,\n\nCurrently the -j option to pg_restore, which allows for parallelization in\nthe restore, can only be used if the input file is a regular file and not,\nfor ex., a pipe. However this is a pretty common occurrence for us\n(usually in the form of pg_dump | pg_restore to copy an indiv... |
[
{
"msg_contents": "The primary change we made to Postgres in order to support our own\nversion of foreign data wrappers was a row-at-a-time execution for\ntable functions. In standard Postgres, when you execute a table\nfunction, it gathers all of the rows at once and stuffs them into a\nbuffer in order to supp... |
[
{
"msg_contents": "Thanks for the many suggestions on improving the 9.3 release notes.\nThere were many ideas I would have never thought of. Please keep the\nsuggestions coming.\n\n-- \n Bruce Momjian <bruce@momjian.us> http://momjian.us\n EnterpriseDB http://enterprisedb.... |
[
{
"msg_contents": "Hi,\n\nI find problem about failing start-up achive recovery at Standby mode in PG9.2.4 streaming replication.\nI test same problem in PG9.2.3. But it is not occerd...\n\nWe search this problem patch in PostgreSQL git repository.\nIt may be occerd in this commit.\nhttp://git.postgresql.org/gi... |
[
{
"msg_contents": "Make fast promotion the default promotion mode.\nContinue to allow a request for synchronous\ncheckpoints as a mechanism in case of problems.\n\nBranch\n------\nmaster\n\nDetails\n-------\nhttp://git.postgresql.org/pg/commitdiff/2317a63328cd9d1c22d02218c6959f340b63d98f\n\nModified Files\n----... |
[
{
"msg_contents": "Hi,\n\nour internal testbuilds show a new warning on windows:\nsrc\\bin\\psql\\command.c(2617): warning C4013: 'time' undefined; assuming extern returning int [C:\\jenkins\\workspace\\andres_git.postgresql.org_windows\\BT\\release\\SL_OS\\windows\\TA\\x86\\TO\\xp\\psql.vcxproj]\nsrc\\bin\\psq... |
[
{
"msg_contents": "With the stats file split patch 187492b6c2e8cafc5 introduced in 9.3dev, now\nafter a crash the postmaster will try to delete all files in the directory\nstats_temp_directory. When that is just a subdirectory of PGDATA, this is\nfine. But it seems rather hostile when it is set to a shared dir... |
[
{
"msg_contents": "Folks,\n\nThe 2013 cluster-hackers meeting is less than a month away. If you are\nattending, and have topics of common interest to discuss, such as core\nAPIs (i.e. event triggers are in, at least partway), please add your\ntopic to the wiki here:\n\nhttps://wiki.postgresql.org/wiki/PgCon201... |
[
{
"msg_contents": "Silly typo report. Line 3774 of lmgr's lock.c says:\n\n * Re-acquire a lock belonging to a transaction that was prepared, when\n * when starting up into hot standby mode.\n\nThis has been the case since the original hot standby commit.\n\n-- \nPeter Geoghegan\n\n\n-- \nSent via pgsql-hackers ... |
[
{
"msg_contents": "After reviewing the threads and thinking about the various\nhistorical behaviors, I'm suggesting that we apply the attached,\nback-patched to 9.0, to fix the unintended changes from historical\nbehavior related to lack of statistics generation in some cases\nwhere statistics were generated be... |
[
{
"msg_contents": "Recently we encountered the following unhappy sequence of events:\n\n1/ system running happily\n2/ batch load into table begins\n3/ very quickly (some) preexisting queries on said table go orders of \nmagnitude slower\n4/ database instance becomes unresponsive\n5/ application outage\n\nAfter ... |
[
{
"msg_contents": "I'm not sure who is supposed to be able to read this sort of stuff:\n\nLatest checkpoint's NextXID: 0/7575\nLatest checkpoint's NextOID: 49152\nLatest checkpoint's NextMultiXactId: 7\nLatest checkpoint's NextMultiOffset: 13\nLatest checkpoint's oldestXID: 1265\nLate... |
[
{
"msg_contents": "I explain more detail about this problem.\n\nThis problem was occurred by RestartPoint create illegal WAL file in during\narchive recovery. But I cannot recognize why illegal WAL file was created\nin CreateRestartPoint(). My attached patch is really plain…\n\nIn problem case at XLogFileReadAn... |
[
{
"msg_contents": "Hi All,\nIf group by clause has primary key, the targetlist may have columns which\nare not part of the aggregate and not part of group by clause. The relevant\ncommit is e49ae8d3bc588294d07ce1a1272b31718cfca5ef and relevant mail thread\nhas subject Functional dependencies and GROUP BY.\n\nAs... |
[
{
"msg_contents": "Fix collation assignment for aggregates with ORDER BY.\n\nORDER BY expressions were being treated the same as regular aggregate\narguments for purposes of collation determination, but really they should\nnot affect the aggregate's collation at all; only collations of the\naggregate's regular ... |
[
{
"msg_contents": "After 87306184580c9c49717, if the postmaster dies without cleaning up (i.e.\npower outage), running \"pg_ctl start\" just gives this message and then\nexits:\n\npg_ctl: another server might be running\n\nUnder the old behavior, it would try to start the server anyway, and\nsucceed, then go th... |
[
{
"msg_contents": "It seems the backend and libpq don't agree. The backend makes no\nspecial provision to wait for a CopyDone message if an error occurs\nduring copy-both. It simply sends an ErrorResponse and that's it.\nlibpq, on the other hand, treats either CopyDone or ErrorResponse as a\ncue to transition... |
[
{
"msg_contents": "These two questions are about the correct coding practice in Postgresql \nvs the specifics of xact.c\n\nIs the main difference between:\n\n if (s->blockState != TBLOCK_SUBINPROGESS)\n elog(*FATAL*, ...\nvs\n Assert(s->blockState == TBLOCK_SUBINPROGRESS);\n\nthe fact that in bo... |
[
{
"msg_contents": "The schedule says we're going to wrap 9.3beta1 on Monday, but it doesn't\nfeel to me like we are anywhere near ready to ship a credible beta.\nOf the items on the 9.3 open-items page,\nhttps://wiki.postgresql.org/wiki/PostgreSQL_9.3_Open_Items\nthere are at least three that seem like absolute... |
[
{
"msg_contents": "Hello All,\nI've been doing some extensive modifications of the storage manager (md.c)\nin postgres. My code all compiles just fine, but when i run initdb, i\nreceive the following output:\n\n\"creating template1 database in /home/accts/wdc22/pgdata/base/1 ... ok\ninitializing pg_authid ... W... |
[
{
"msg_contents": "The pg_resetxlog -m option was changed from\n\n -m XID set next multitransaction ID\n\nto\n\n -m XID,OLDEST set next multitransaction ID and oldest value\n\nbut the man page does not reflect that change.\n\nIt was introduced in 0ac5ad5134f2769ccbaefec73844f8504c4d6182 \"Improve... |
[
{
"msg_contents": "Hi all,\n\nInspired by the awesome work done by Oleg sir in HStore, I have been thinking about making a graph data type as an extension in postgres.\n\nI have been reading about graph databases and how storing data in graphs can lead to some really awesome functionalities such as social netwo... |
[
{
"msg_contents": "After a bit of discussion, the core committee has decided that we're not\nreally ready to wrap a credible beta1 candidate tomorrow. There are\nseveral unresolved issues such as what to do about checksums and\nmatviews; and there seems no good reason to force resolution of\nthese important is... |
[
{
"msg_contents": "Folks,\n\nThe \"FOR ROLE\" syntax is completely broken, as of 9.2.4. Not sure when\nexactly this got broken; I remember it working sometime in the past:\n\n[jberkus@pgx-test ~]$ psql -U postgres analytics2\npsql (9.2.4)\nType \"help\" for help.\n\nanalytics2=# ALTER DEFAULT PRIVILEGES FOR RO... |
[
{
"msg_contents": "On 29 April 2013 01:40, Tom Lane <tgl@sss.pgh.pa.us> wrote:\n> Robert Haas <robertmhaas@gmail.com> writes:\n>> On Sun, Apr 28, 2013 at 11:41 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:\n>>> Well, it's fairly clear *how* to do it: add some more processing that\n>>> occurs after we've completed cra... |
[
{
"msg_contents": "Hello,\n\nPlease find attached a small patch to add a throttling capability to \npgbench, that is pgbench aims at a given client transaction rate instead \nof maximizing the load. The throttling relies on Poisson-distributed \ndelays inserted after each transaction.\n\nI wanted that to test t... |
[
{
"msg_contents": "Existing:\n\npg_get_constraintdef\npg_get_indexdef\npg_get_viewdef\npg_get_triggerdef\npg_get_functiondef\npg_get_ruledef\n\nMissing:\n\npg_get_ts_templatedef\npg_get_ts_parserdef\npg_get_ts_configdef\npg_get_ts_dictdef\npg_get_databasedef\npg_get_namespacedef\npg_get_languagedef\npg_get_conv... |
[
{
"msg_contents": "Revert \"pg_ctl: Add idempotent option\"\n\nThis reverts commit 87306184580c9c49717b00d48a2f9e717f21e0a8. The\nbehavior in certain cases is still being debated, and it's too late to\nsolve this before beta.\n\nBranch\n------\nmaster\n\nDetails\n-------\nhttp://git.postgresql.org/pg/commitdif... |
[
{
"msg_contents": "The following bug has been logged on the website:\n\nBug reference: 8128\nLogged by: Adrian Vondendriesch\nEmail address: Adrian.Vondendriesch@credativ.de\nPostgreSQL version: 9.1.9\nOperating system: Debian GNU/Linux 7.0\nDescription: \n\nHi,\n\nwhile browsing on ... |
[
{
"msg_contents": "On Tue, Apr 30, 2013 at 10:40 AM, Kevin Grittner <kgrittn@ymail.com> wrote:\n> \"Staleness\" is a completely different issue, in my view, from\n> quietly returning results that are not, and never were, accurate.\n> Sure we need to implement more refined \"scannability\" tests than\n> whether ... |
[
{
"msg_contents": "Add regression test for bug fixed by recent refactoring.\n\nTest case by Andres Freund for bug fixed by Tom Lane's refactoring\nin commit 5194024d72f33fb209e10f9ab0ada7cc67df45b7\n\nBranch\n------\nmaster\n\nDetails\n-------\nhttp://git.postgresql.org/pg/commitdiff/200ba1667b3a8d7a9d559d2f05f... |
[
{
"msg_contents": "I think that at\nhttp://www.postgresql.org/docs/current/static/functions-admin.html and\nhttp://www.postgresql.org/docs/current/static/continuous-archiving.html two\nimportant points on how pg_start_backup() works are missing:\n\n1. After pg_start_backup() and till pg_stop_backup() VACUUM is ... |
[
{
"msg_contents": "Seems like this might be a good idea to avoid the type of failure\nexhibited in bug #8128. We don't care too much about the readability\nof the dump script created during an upgrade, so it's hard to see a\ndownside.\n\n\t\t\tregards, tom lane\n\n\n-- \nSent via pgsql-hackers mailing list (pg... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.