threads listlengths 1 2.99k |
|---|
[
{
"msg_contents": "I am looking at adding an index tuple flag to indicate when a heap tuple\nis expired so the index code can skip looking up the heap tuple.\n\nThe problem is that I can't figure out how be sure that the heap tuple\ndoesn't need to be looked at by _any_ backend. Right now, we update the\ntrans... |
[
{
"msg_contents": "I think the restore process could be made more error proof if the following \nadditions could be made:\n\npg_dump, (maybe started with a special flag) if run with superuser rights \nshould not issue\n\n\\connect - username\ncreate table foo (...\ncopy foo from ...\n\nto create tables, but use... |
[
{
"msg_contents": "CVSROOT:\t/home/projects/pgsql/cvsroot\nModule name:\tpgsql\nChanges by:\tpetere@hub.org\t01/05/17 13:44:18\n\nModified files:\n\tdoc/src/sgml : runtime.sgml \n\tsrc/backend/utils/fmgr: Makefile dfmgr.c \n\tsrc/backend/utils/misc: guc.c \n\tsrc/include : fmgr.h \n\nLog message:\n\tAdd dy... |
[
{
"msg_contents": "Jeremy Blumenfeld (jeremy@horizonlive.com) reports a bug with a severity of 1\nThe lower the number the more severe it is.\n\nShort Description\nProblems with avg on interval data type\n\nLong Description\nWe have recently upgraded from 7.0.3 to 7.1 and a query which used to work is no longer... |
[
{
"msg_contents": "I've been noticing that the information in the HISTORY file is regularly\nincomplete, not understandable, and mostly useless except for \"wow, look\nwhat we've done\" purposes. When we get to a release a year from now\n(*grin*) I'm sure the dynamic_library_path thing is going to end up under... |
[
{
"msg_contents": "I have been thinking about the problem of VACUUM and how we might fix it\nfor 7.2. Vadim has suggested that we should attack this by implementing\nan overwriting storage manager and transaction UNDO, but I'm not totally\ncomfortable with that approach: it seems to me that it's an awfully lar... |
[
{
"msg_contents": "Very neat. You mention that the truncation of both heap and index \nrelations is not necessarily mandatory. Under what conditions would \neither of them be truncated?\n\nMike Mascari\nmascarm@mascari.com\n\n-----Original Message-----\nFrom:\tTom Lane [SMTP:tgl@sss.pgh.pa.us]\n\n....\n\n3. Laz... |
[
{
"msg_contents": "Hello,\n\nI've noticed that all custom operators or inet type (such as <<, <<=, etc) \ncannot use an index, even though it is possible to define such an\noperation on an index, for ex:\nX << Y can be translated to \"X >= network(Y) && X <= broadcast(Y)\" (or so)\n\nAccording to docs, postgre... |
[
{
"msg_contents": "\n> I am looking at adding an index tuple flag to indicate when a \n> heap tuple is expired so the index code can skip looking up the heap tuple.\n> \n> The problem is that I can't figure out how be sure that the heap tuple\n> doesn't need to be looked at by _any_ backend. Right now, we upda... |
[
{
"msg_contents": "\nWhen organizing available free storage for re-use, we will probably have\na choice whether to favor using space in (mostly-) empty blocks, or in \nmostly-full blocks. Empty and mostly-empty blocks are quicker -- you \ncan put lots of rows in them before they fill up and you have to choose ... |
[
{
"msg_contents": "\n> > ???? Isn't current implementation \"bulk delete\" ?\n> \n> No, the index AM is called separately for each index tuple to be\n> deleted; more to the point, the search for deletable index tuples\n> should be moved inside the index AM for performance reasons.\n\nWouldn't a sequential scan ... |
[
{
"msg_contents": "\n> A particular point worth making is that in the common case where you've\n> updated the same row N times (without changing its index key), the above\n> approach has O(N^2) runtime. The indexscan will find all N index tuples\n> matching the key ... only one of which is the one you are look... |
[
{
"msg_contents": "set digest\n\n",
"msg_date": "Fri, 18 May 2001 08:25:50 -0700",
"msg_from": "Fernando Cabrera <fcabrera@dmvlink.com>",
"msg_from_op": true,
"msg_subject": "None"
}
] |
[
{
"msg_contents": "\n> There was some discussion of doing that, but it fell down on the little\n> problem that in normal index-search cases you *don't* know the heap tid\n> you are looking for.\n\nI can not follow here. It does not matter if you don't know a trailing \npart of the key when doing a btree search,... |
[
{
"msg_contents": "\n> > > I am looking at adding an index tuple flag to indicate when a \n> > > heap tuple is expired so the index code can skip looking up the heap tuple.\n> > > \n> > > The problem is that I can't figure out how be sure that the heap tuple\n> > > doesn't need to be looked at by _any_ backend.... |
[
{
"msg_contents": "> FYI, the code was warning about psql backslash command usage:\n> \n> /*\n> * If the command was not recognized, try to parse it as a one-letter\n> * command with immediately following argument (a still-supported,\n> * but no longer encouraged, syntax).\n> ... |
[
{
"msg_contents": "I've been going talking with the SGI technical support about some of the\nerrors I got when compiling Postgres 7.1.1 on SGI IRIX 6.5.12 with the\nMIPSPro 7.3 C compiler. I've already mentioned that somehow the compiler\ncan't see the correct definition for strdup (I believe she thought that\n... |
[
{
"msg_contents": "\tAnyone know what the default password is for the postgres user? When\ntrying to use createuser, the password for the postgres user is asked. What\nis that default password? I searched all through the docs but couldn't find\nit.\n \nThanks.\n\n\n",
"msg_date": "Fri, 18 May 2001 12:03:27 ... |
[
{
"msg_contents": "\nIs anyone using the define OLD_FILE_NAMING? Seems we can remove the\ntest now.\n\n-- \n Bruce Momjian | http://candle.pha.pa.us\n pgman@candle.pha.pa.us | (610) 853-3000\n + If your life is a hard drive, | 830 Blythe Avenue\n + Christ can b... |
[
{
"msg_contents": "Will anyone object if I change the calling convention for operator\nselectivity estimation functions (oprrest, oprjoin entries in\npg_operator)?\n\nHistorically the call conventions have been\n\ndouble oprrest(Oid opid, Oid relid, AttrNumber attno,\n\t\tDatum value, int32 flag);\n\ndouble opr... |
[
{
"msg_contents": "I have an external search engine system which plugs in to postgres. I use a few\nC functions to interface the search daemon with the Postgres back-end.\n\nThe best that I have been able to do is do a \"select\" for each result. I have a\nlive demo/test site:\n\nhttp://www.mohawksoft.com/searc... |
[
{
"msg_contents": "> I have been thinking about the problem of VACUUM and how we \n> might fix it for 7.2. Vadim has suggested that we should\n> attack this by implementing an overwriting storage manager\n> and transaction UNDO, but I'm not totally comfortable with\n> that approach: it seems to me that it's an... |
[
{
"msg_contents": "> I see postgres 7.1.1 is out now. Was the fix for this\n> problem included in the new release?\n\nI fear it will be in 7.2 only.\n\n> On Thursday 29 March 2001 20:02, Philip Warner wrote:\n> > At 19:14 29/03/01 -0800, Mikheev, Vadim wrote:\n> > >> >Reported problem is caused by bug (only on... |
[
{
"msg_contents": "> Vadim, can you remind me what UNDO is used for?\n\nOk, last reminder -:))\n\nOn transaction abort, read WAL records and undo (rollback)\nchanges made in storage. Would allow:\n\n1. Reclaim space allocated by aborted transactions.\n2. Implement SAVEPOINTs.\n Just to remind -:) - in the eve... |
[
{
"msg_contents": "Greetings,\n I have made the following table(s),indexes,etc. I wonder if there\nis an index (or something else), I can create to make the query use a\n\"better\" plan. (not that it's slow at the moment, but as the table\ngrows...). \n\nSchema:\n\n--\n-- Selected TOC Entries:\n--\n\\conne... |
[
{
"msg_contents": "We have on the TODO list:\n\n\t* SELECT pg_class FROM pg_class generates strange error\n\nIt passes the tablename as targetlist all the way to the executor, where\nit throws an error about Node 704 unkown.\n\nThis patch fixes the problem by generating an error in the parser:\n\n\ttest=> selec... |
[
{
"msg_contents": "Hi,\n\nI managed to drop really important table. Fortunately, I had a backup of\nthe table (raw #### file, not a ascii file). After putting that table into\nfreshly initdb'd database, postgres doesn't see new transactions even\nthough 'vacuum' sees the tuples alright. \n\nSo, question. I'd li... |
[
{
"msg_contents": "I've sent this a few weeks ago and got support, I just wanted to issue the\nfinal call.\n\nSQL and Postgres differ in behaviour if the value of a char or varchar\ntype exceeds the declared length. Postgres cuts off the value, SQL\nrequires to raise an error.\n\nIn particular, the compliant b... |
[
{
"msg_contents": "I tried to do a TRUNCATE on a table that was referenced by other table and\nthe refererential integrity wasn't kept. Seems to me this thing behaves\nreally differently then DELETE FROM table. I think it should be at least\nmentioned in the docs or disabled if the table is referenced by foreig... |
[
{
"msg_contents": "Is any support for reworking the postgres headers such that they can be used,\ncleanly, in a C++ program?\n",
"msg_date": "Sat, 19 May 2001 10:21:27 -0400",
"msg_from": "mlw <markw@mohawksoft.com>",
"msg_from_op": true,
"msg_subject": "C++ Headers"
},
{
"msg_contents":... |
[
{
"msg_contents": "Sorry to gripe here. Don't get me wrong, I think Postgres is amazing, and I\nthink all you guys do an amazing job. \n\nIs it just me, or do others agree, functions returning sets need to be able to\nbe used in a select where equal clause.\n\nselect * from table where field = funct_set('bla bl... |
[
{
"msg_contents": "I see Tom Lane implemented the SQL92 feature of using subselects in \nFROM clauses:\n\nCREATE TABLE foo (\nkey integer not null,\nvalue text);\n\nSELECT * FROM (SELECT * FROM foo) AS bar\nWHERE bar.key = 1;\n\nPerhaps this is how functions returning sets should operate:\n\nSELECT titles.* FRO... |
[
{
"msg_contents": "Hi all,\n\nAttached is my patch that adds DROP CONSTRAINT support to PostgreSQL. I\nbasically want your guys feedback. I have sprinkled some of my q's thru\nthe text delimited with the @@ symbol. It seems to work perfectly.\n\nAt the moment it does CHECK constraints only, with inheritance.... |
[
{
"msg_contents": "Hello,\n\nAs I understand it:\nIssuing a �select for update� within a transaction will prevent other users\nfrom modifying data. (exclusive lock)\n\nI�m contemplating using the DBI interface as a permanent client to postgres\nfor a group of users, and have a few questions.\n\nWill the a... |
[
{
"msg_contents": "As long as you're fixing bugs in pgindent, here are some more follies\nexhibited by the most recent pgindent run. Some of these bugs have\nbeen there for awhile, but at least one (the removal of space before\na same-line comment) seems to be new as of the most recent run.\n\nThe examples are... |
[
{
"msg_contents": "If I create an index based on a function, as:\n\ncreate index fubar on table (function(field));\n\nand then I later:\n\ndrop function function(...);\n\nIt makes it impossible to pg_dump a database until one also explicitly drops\nthe index. This happens in 7.0 and I haven't checked it 7.1.\n\... |
[
{
"msg_contents": "While we're on the subject of new system catalogs, how about a many to many\ncatalog like this:\n\npg_depend (oid obj, oid dep)\n\nThat maps the oid of a system object (such as a constraint, index, function,\ntrigger, anything) to all other system objects that are dependent upon it.\nAlthough... |
[
{
"msg_contents": "Hi All ,\n\nSELECT DISTINCT h_name FROM haszon;\n+---------------+\n| h_name |\n+---------------+\n| CITROEN |\n| DAEWOO-FSO |\n| DAEWOO-LUBLIN |\n| FIAT |\n| FORD |\n| GAZ |\n| HYUNDAI |\n| KIA |\n| MAZDA |\n| MERCEDES BENZ ... |
[
{
"msg_contents": "Hi.\n\nWe tried the RPM under RH 6.2 and it would unpack, saying we needed this or\nthat or the other... A whole bunch of dependencies.\n\nAnyway, once of us downloaded the source and compiled it and it worked...\n\nI just want to be sure... there's no compelling reason to use RH 7.x\n(basica... |
[
{
"msg_contents": "\n>> I don't know what you are using those database for, but nothing prevents\n> >you from letting your clients connect to the different databases the\n> >same time.\n\n\n>But that requires me to make a new database connection for each database I\n>need to access.\n\n>And putting 200+ tables ... |
[
{
"msg_contents": "Apologises if I've missed something, but isn't that the same xmin that ODBC\nuses for row versioning?\n- Stuart\n\n\t<Snip>\n> Currently, the XMIN/XMAX command counters are used only by the current\n> transaction, and they are useless once the transaction finishes and take\n> up 8 bytes on di... |
[
{
"msg_contents": "\n> > Vadim, can you remind me what UNDO is used for?\n> 4. Split pg_log into small files with ability to remove old ones (which\n> do not hold statuses for any running transactions).\n\nThey are already small (16Mb). Or do you mean even smaller ?\nThis imposes one huge risk, that is alrea... |
[
{
"msg_contents": "\n> > > Vadim, can you remind me what UNDO is used for?\n> > 4. Split pg_log into small files with ability to remove old ones (which\n> > do not hold statuses for any running transactions).\n\nand I wrote:\n> They are already small (16Mb). Or do you mean even smaller ?\n\nSorry for above l... |
[
{
"msg_contents": "Hi folks,\n\n I just committed changes to the SPI manager and PL/pgSQL,\n providing full CURSOR support. A detailed description is\n attached as a Postscript file. Brief description follows.\n\n Enhancement of SPI:\n\n There are a couple of new functions and internal... |
[
{
"msg_contents": "\n> > I tend to agree that we should not change the code to make \"select tab\"\n> > work, on the grounds of error-proneness.\n> \n> OK, here is another patch that does this:\n> \n> \ttest=> select test from test;\n> \t test \n> \t------\n> \t 1\n> \t(1 row)\n\nI object also. It is not a f... |
[
{
"msg_contents": "I just upgraded PostgreSQL from 21 March CVS (rc1?) to May 19 16:21 GMT CVS.\nI found that all my cgi/fcg scripts which use libpq++ stopped working in\nthe vague sense of apache mentioning an internal server error. Relinking\nthem cured the problem (had to do this in haste => unfortunately no... |
[
{
"msg_contents": "\n> True, although there's a certain inconsistency in allowing a whole row\n> to be passed to a function by\n> \n> \tselect foo(pg_class) from pg_class;\n> \n> and not allowing the same row to be output by\n\nImho there is a big difference between the two. The foo(pg_class) calls a function \... |
[
{
"msg_contents": "Every once in a while some user complains that \"the cursor keys don't work\nanymore in psql\". There has even been one case where a major vendor has\nshipped binaries without readline support. While we keep telling them,\n\"make sure configure finds the library and the header files\", this... |
[
{
"msg_contents": "\n> Tom Lane wrote:\n> > \n> > begin;\n> > select * from foo where x = functhatreadsbar();\n\nI thought that the per statement way to do it with a non cacheable function was:\n\tselect * from foo where x = (select functhatreadsbar());\n\n??\nAndreas\n\nPS: an iscacheable funct... |
[
{
"msg_contents": "\n> Really?! Once again: WAL records give you *physical* address of tuples\n> (both heap and index ones!) to be removed and size of log to read\n> records from is not comparable with size of data files.\n\nSo how about a background \"vacuum like\" process, that reads the WAL\nand does the cle... |
[
{
"msg_contents": "\n> Would it be possible to split the WAL traffic into two sets of files,\n\nSure, downside is two fsyncs :-( When I first suggested physical log \nI had a separate file in mind, but that is imho only a small issue.\n\nOf course people with more than 3 disks could benefit from a split.\n\nTom... |
[
{
"msg_contents": "\n> My point is that we'll need in dynamic cleanup anyway and UNDO is\n> what should be implemented for dynamic cleanup of aborted changes.\n\nI do not yet understand why you want to handle aborts different than outdated\ntuples. The ratio in a well tuned system should well favor outdated tup... |
[
{
"msg_contents": "\n> > Tom: If your ratio of physical pages vs WAL records is so bad, the config\n> > should simply be changes to do fewer checkpoints (say every 20 min like a \n> > typical Informix setup).\n> \n> I was using the default configuration. What caused the problem was\n> probably not so much the ... |
[
{
"msg_contents": "> > Really?! Once again: WAL records give you *physical*\n> > address of tuples (both heap and index ones!) to be\n> > removed and size of log to read records from is not\n> > comparable with size of data files.\n> \n> So how about a background \"vacuum like\" process, that reads\n> the WAL a... |
[
{
"msg_contents": "We have a TODO item\n\t* Update reltuples in COPY\n\nI was just about to go do this when I realized that it may not be such\na hot idea after all. The problem is that updating pg_class.reltuples\nmeans that concurrent COPY operations will block each other, because\nthey want to update the sa... |
[
{
"msg_contents": "> > It probably will not cause more IO than vacuum does right now.\n> > But unfortunately it will not reduce that IO.\n> \n> Uh ... what? Certainly it will reduce the total cost of vacuum,\n> because it won't bother to try to move tuples to fill holes.\n\nOh, you're right here, but daemon wi... |
[
{
"msg_contents": "> I hope we can avoid on-disk FSM. Seems to me that that would create\n> problems both for performance (lots of extra disk I/O) and reliability\n> (what happens if FSM is corrupted? A restart won't fix it).\n\nWe can use WAL for FSM.\n\nVadim\n",
"msg_date": "Mon, 21 May 2001 09:55:40 -... |
[
{
"msg_contents": "Jan Wieck <JanWieck@yahoo.com> writes:\n> I think the in-shared-mem FSM could have some max-per-table\n> limit and the background VACUUM just skips the entire table\n> as long as nobody reused any space.\n\nI was toying with the notion of trying to use Vadim's \"MNMB\" idea... |
[
{
"msg_contents": "> From: Mikheev, Vadim \n> Sent: Monday, May 21, 2001 10:23 AM\n> To: 'Jan Wieck'; Tom Lane\n> Cc: The Hermit Hacker; 'Bruce Momjian';\n> pgsql-hackers@postgresql.orgrg.us.greatbridge.com\n\nStrange address, Jan?\n\n> Subject: RE: [HACKERS] Plans for solving the VACUUM problem\n> \n> \n> > ... |
[
{
"msg_contents": "> > We could keep share buffer lock (or add some other kind of lock)\n> > untill tuple projected - after projection we need not to read data\n> > for fetched tuple from shared buffer and time between fetching\n> > tuple and projection is very short, so keeping lock on buffer will\n> > not imp... |
[
{
"msg_contents": "> > My point is that we'll need in dynamic cleanup anyway and UNDO is\n> > what should be implemented for dynamic cleanup of aborted changes.\n> \n> I do not yet understand why you want to handle aborts different than\n> outdated tuples.\n\nMaybe because of aborted tuples have shorter Time-To... |
[
{
"msg_contents": "Hi folks,\n\n I just committed changes to the SPI manager and PL/pgSQL,\n providing full CURSOR support. A detailed description is\n attached as a Postscript file. Brief description follows.\n\n#\n# Note:\n# The version with the attachment didn't make it up to now.\n# Resend... |
[
{
"msg_contents": "> > We could keep share buffer lock (or add some other kind of lock)\n> > untill tuple projected - after projection we need not to read data\n> > for fetched tuple from shared buffer and time between fetching\n> > tuple and projection is very short, so keeping lock on buffer will\n> > not imp... |
[
{
"msg_contents": "> Correct me if I am wrong, but both cases do present a problem\n> currently in 7.1. The WAL log will not remove any WAL files\n> for transactions that are still open (even after a checkpoint\n> occurs). Thus if you do a bulk insert of gigabyte size you will\n> require a gigabyte sized WAL d... |
[
{
"msg_contents": "I know this is not an \"on-topic\" post, but I wanted my message to reach the\nright people.\n\nI want to thank all of you who have worked so hard to make Postgres such an\nexcellent database. Since people tend to complain a lot, I thought it might\nbe nice to share some good news...\n\nI ha... |
[
{
"msg_contents": "Hi,\n\nI need grant access on my DB to many users that's can SELECT, UPDATE,\nINSERT or DELETE over tables, and viwes. This point, all OK.\n\nBut I don't wan't this users can create new tables on my DB.\n\nWhere can I do that ???\n\n\nRegards,\n\nTulio Oliveira\n\n\n-- \nUm velho homem s�bi... |
[
{
"msg_contents": "\n> We have a TODO item\n> \t* Update reltuples in COPY\n> \n> I was just about to go do this when I realized that it may not be such\n> a hot idea after all.\n\nImho it is not a good idea at all. The statistics are a very sensitive area,\nthat imho should only be calculated on request. I alr... |
[
{
"msg_contents": "Just thought that I'd tell you.\n\nI've been waiting (very patiently, I think) for a long time for outre joins, \nviews w/ joins and not the least, functions that can handle NULL's in an \norderly way.\n\nA little anxious I started implementing these elements in my projects, \nremoving the wo... |
[
{
"msg_contents": "\n> Correct me if I am wrong, but both cases do present a problem currently \n> in 7.1. The WAL log will not remove any WAL files for transactions that \n> are still open (even after a checkpoint occurs). Thus if you do a bulk \n> insert of gigabyte size you will require a gigabyte sized WA... |
[
{
"msg_contents": "\n> As a rule of thumb, online applications that hold open\n> transactions during user interaction are considered to be\n> Broken By Design (tm). So I'd slap the programmer/design\n> team with - let's use the server box since it doesn't contain\n> anything ... |
[
{
"msg_contents": " \n> REDO in oracle is done by something known as a 'rollback segment'. \n\nYou are not seriously saying that you like the \"rollback segments\" in Oracle.\nThey only cause trouble: \n1. configuration (for every different workload you need a different config) \n2. snapshot too old \n3. tx ab... |
[
{
"msg_contents": "> Todo:\n> \n> 1. Compact log files after checkpoint (save records of uncommitted\n> transactions and remove/archive others).\n\nOn the grounds that undo is not guaranteed anyway (concurrent heap access),\nwhy not simply forget it, since above sounds rather expensive ?\nThe downside would ... |
[
{
"msg_contents": "\n> Explicit cursor can be declared as:\n> \n> DECLARE\n> ...\n> curname CURSOR [(argname type [, ...])]\n> IS <select_stmt>;\n\nIn esql you would have FOR instead of IS.\n\nDECLARE curname CURSOR ... FOR ....\n\nThus the quest... |
[
{
"msg_contents": "> However, just remember that pg_class already has a row count that we\n> force in there by default.\n\n> I was just suggesting we make that accurate if we can, even if we can\n> make it accurate only 80% of the time. Once we INSERT, it isn't\n> accurate anymore anyway. This is just an esti... |
[
{
"msg_contents": "Off topic, but I thought this was interesting. This is information\nabout compiling OpenOffice. Hope PostgreSQL never gets to be this size:\n\n http://www.openoffice.org/FAQs/build_faq.html\n\n---------------------------------------------------------------------------\n\n\tHow much hard ... |
[
{
"msg_contents": "One other data point:\n\n---------------------------------------------------------------------------\n\t\n\tHow much source code is there? \n\t\n\tOpenOffice source will have approx. 20,000 source files. \n\t\n\tOpenOffice will have approx. 7,600,000 lines of code. The majority of\n\tthe cod... |
[
{
"msg_contents": "I asked this question on General/Questions about a week ago, I've done \na bit more testing since, but still can't get things to work properly. \nNoone answered on the other group and a search of the archives did not \nturn up anything even remotely similar.\n\nSystem:\n\nSolaris 7, patched ... |
[
{
"msg_contents": "\nftp://ftp.postgresql.org/pub/source/v7.1.2 ...\n\nJust want a second opinion before I announce more publicly ...\n\nThanks ...\n\nMarc G. Fournier ICQ#7615664 IRC Nick: Scrappy\nSystems Administrator @ hub.org\nprimary: scrappy@hub.org secondary: sc... |
[
{
"msg_contents": "Hi you all:\n\nI�ve got some kind of a problem in the deploy of my perl client.\nMy environment is the following\nIhave a Solaris 7 web server in the internet, powered by apache and outside the local net.\n>From it I can access, through a hole in the firewall to my PostgreSQL 7.0.2 (yes, Iï... |
[
{
"msg_contents": "\nThis timezone fix was applied to jdbc2 in 7.1.2 by Thomas. Do you want\nthis in jdbc1 also? I am not recommending it, just asking to make sure\nit wasn't overlooked.\n\n---------------------------------------------------------------------------\n\nrevision 1.22.2.1\ndate: 2001/05/22 14:46... |
[
{
"msg_contents": "> > 1. Compact log files after checkpoint (save records of uncommitted\n> > transactions and remove/archive others).\n> \n> On the grounds that undo is not guaranteed anyway (concurrent\n> heap access), why not simply forget it,\n\nWe can set flag in ItemData and register callback function... |
[
{
"msg_contents": "\nI see some use of SEP_CHAR for '/' in the source. Do we want to use it\nconsistenly, or not use it at all? I can make the change.\n\n-- \n Bruce Momjian | http://candle.pha.pa.us\n pgman@candle.pha.pa.us | (610) 853-3000\n + If your life is a har... |
[
{
"msg_contents": "http://www.postgresql.org/~petere/gettext.html\n\nThis is a compilation of the BSD-licensed gettext tools from NetBSD plus\nsome of my own code, put into a (hopefully) portable package, intended to\nbe evaluated for possible use in PostgreSQL. Give it a try if you're\ninterested. I've alrea... |
[
{
"msg_contents": "\nFolks:\n As I study the source of LockBuffer in bufmgr.c I came across\nthe following code snippet for the case of releasing a\nshared (read) lock:\n\n\n if (mode == BUFFER_LOCK_UNLOCK)\n {\n if (*buflock & BL_R_LOCK)\n {\n ... |
[
{
"msg_contents": "> (buf->r_locks)--;\n> if (!buf->r_locks)\n> *buflock &= ~BL_R_LOCK;\n> \n> \n> Or I am missing something...\n\nbuflock is per-backend flag, it's not in shmem. Backend is\nallowed only single lock per buffer.\n\nV... |
[
{
"msg_contents": "> > And, I cannot say that I would implement UNDO because of\n> > 1. (cleanup) OR 2. (savepoints) OR 4. (pg_log management)\n> > but because of ALL of 1., 2., 4.\n> \n> OK, I understand your reasoning here, but I want to make a comment.\n> \n> Looking at the previous features you added, like ... |
[
{
"msg_contents": "love to have a copy of that script that backups postgre remotely. \n\nangel\n\n\n\n\n\n\n\nlove to have a copy of that script that backups \npostgre remotely. \n \nangel",
"msg_date": "Tue, 22 May 2001 16:51:24 -0700",
"msg_from": "\"roger\" <administrator@hollywoodmistress.com>",... |
[
{
"msg_contents": "Has this been already fixed or reported?\n\n---------------------------------------------------------\nWelcome to psql, the PostgreSQL interactive terminal.\n\nType: \\copyright for distribution terms\n \\h for help with SQL commands\n \\? for help on internal slash commands\n ... |
[
{
"msg_contents": "Can someone point me to an active postgres listing......\n\nthis one seems a bit �slow�....(no offense intended)... \n\n\n\nanyone actively follow this group?\n\n\nCan someone point me to an active postgres listing......\n\nthis one seems a bit “slow”....(no offense intended)...",
"ms... |
[
{
"msg_contents": "\n> If community will not like UNDO then I'll probably try to implement\n\nImho UNDO would be great under the following circumstances:\n\t1. The undo is only registered for some background work process\n\t and not done in the client's backend (or only if it is a small txn).\n\t2. The same ... |
[
{
"msg_contents": "> > People also have referred to an overwriting smgr\n> > easily. Please tell me how to introduce an overwriting smgr\n> > without UNDO.\n\nThere is no way. Although undo for an overwriting smgr would involve a\nvery different approach than with non-overwriting. See Vadim's post about what \n... |
[
{
"msg_contents": "\n> > The downside would only be, that long running txn's cannot\n> > [easily] rollback to savepoint.\n> \n> We should implement savepoints for all or none transactions, no?\n\nWe should not limit transaction size to online available disk space for WAL. \nImho that is much more important. Wit... |
[
{
"msg_contents": "At 14:33 22/05/01 -0700, Mikheev, Vadim wrote:\n>\n>If community will not like UNDO then I'll probably try to implement\n>dead space collector which will read log files and so on. \n\nI'd vote for UNDO; in terms of usability & friendliness it's a big win.\nTom's plans for FSM etc are, at leas... |
[
{
"msg_contents": "\n> >If community will not like UNDO then I'll probably try to implement\n> >dead space collector which will read log files and so on. \n> \n> I'd vote for UNDO; in terms of usability & friendliness it's a big win.\n\nCould you please try it a little more verbose ? I am very interested in \nt... |
[
{
"msg_contents": "At 11:25 23/05/01 +0200, Zeugswetter Andreas SB wrote:\n>\n>> >If community will not like UNDO then I'll probably try to implement\n>> >dead space collector which will read log files and so on. \n>> \n>> I'd vote for UNDO; in terms of usability & friendliness it's a big win.\n>\n>Could you pl... |
[
{
"msg_contents": "\nset_inherited_rel_pathlist in src/backend/path/allpaths.c says:\n\n /*\n * XXX for now, can't handle inherited expansion of FOR UPDATE; can we\n * do better?\n */\n\nIs this a terribly difficult thing to implement?\n\nThe RI triggers use FOR UPDATE which makes RI impossible with\ninherit... |
[
{
"msg_contents": "\n> - A simple typo in psql can currently cause a forced rollback of the entire\n> TX. UNDO should avoid this.\n\nYes, I forgot to mention this very big advantage, but undo is not the only possible way \nto implement savepoints. Solutions using CommandCounter have been discussed.\nAlthough th... |
[
{
"msg_contents": "\npg_dump's help provides this near the bottom:\n\nIf no database name is not supplied, then the PGDATABASE environment\nvariable value is used.\n\nShouldn't that read:\n\nIf no database name is supplied, then the PGDATABASE environment\nvariable value is used.\n\nor:\n\nIf the database name ... |
[
{
"msg_contents": "This is resent of my messages I sent by mistake to BUGS list\n\n\tRegards,\n\t\tOleg\n_____________________________________________________________\nOleg Bartunov, sci.researcher, hostmaster of AstroNet,\nSternberg Astronomical Institute, Moscow University (Russia)\nInternet: oleg@sai.msu.su,... |
[
{
"msg_contents": "On Wed, May 23, 2001 at 11:35:31AM -0400, Bruce Momjian wrote:\n> > > > > We have added more const-ness to libpq++ for 7.2.\n> > > > \n> > > > Breaking link compatibility without bumping the major version number\n> > > > on the library seems to me serious no-no.\n> > > > \n> > > > To const-if... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.