threads listlengths 1 2.99k |
|---|
[
{
"msg_contents": "\nHi,\n\nI've just found very suspicious directory entries in\nftp.postgresql.org/pub/.incoming, for sure it's an attempt to exploit some\nsecuirity hole to gain access to your machine or machines mirroring the FTP\nsite. The entries seems to be here for a lot of time, but I didn't seem to se... |
[
{
"msg_contents": "Hi,\n\nShot, Leon. The patch removes the #define YY_USES_REJECT from scan.c, which\nmeans we now have expandable tokens. Of course, it also removes the\nscanning of \"embedded minuses\", which apparently causes the optimizer to\nunoptimize a little. However, the next step is attacking the ... |
[
{
"msg_contents": "\n> Hmm,Index scan is chosen to select all rows.\n> AFAIK,sequential scan + sort is much faster than index scan in\n> most cases.\n> \n> \tcost of index scan < cost of sequential scan + cost of sort\n> \nThis is usually true. It might need resources though that are not available,\ne.g. 8 GB s... |
[
{
"msg_contents": ">> > Shot, Leon. The patch removes the #define YY_USES_REJECT from scan.c,\nwhich\n>> > means we now have expandable tokens. Of course, it also removes the\n>> > scanning of \"embedded minuses\", which apparently causes the optimizer\nto\n>> > unoptimize a little. \n>> \n>> Oh, no. Unary mi... |
[
{
"msg_contents": "Sorry, I forgot to mention in the previous mail: I sent patches to the\npatches mailing list (available from the web server), which patch psql, and\nlibpq, and scan.l (except for you patch). The were sent at the beginning of\nthis month, so maybe get them, and see how they work for you.\n\n>... |
[
{
"msg_contents": "As far as I understand it, the MAX_PARSE_BUFFER limit only applies if char\nparsestring[] is used, not if char *parsestring is used. This is the whole\nreason for using flex. And scan.l is set up to compile using char\n*parsestring, not char parsestring[].\n\nThe NAMEDATALEN limit is impose... |
[
{
"msg_contents": "Adam Ulmer <ulmer@soulgamer.com> writes:\n>> can anyone tell me where I need to look so that I can calculate the\n>> amount of shmem req'd by postmaster and N backends?\n\nEasiest way is to try it and see ;-). AFAIR the space allocated per\nbackend is miniscule compared to the space per disk... |
[
{
"msg_contents": "PLEASE does anybody know any sopution how to avoid patholigical grought of\npg_log in 6.5.1.\nI am intensively using begin transactin - end transaction and every 15\nminutes regenerating some tables inside transaction block.\nBut 1 GB of bloat in 10 days is unacceptable.\n\nThank for ANY res... |
[
{
"msg_contents": "Yes, I'll go with that.\n\n>> \n>> Adriaan Joubert wrote:\n>> \n>> > I think NAMEDATALEN referes to the size of a NAME field in \n>> the database,\n>> > which is used to store attribute names etc. So you cannot exceed\n>> > NAMEDATALEN, or the identifier won't fit into the system tables.\n>> ... |
[
{
"msg_contents": ">> \n>> Ansley, Michael wrote:\n>> > \n>> > As far as I understand it, the MAX_PARSE_BUFFER limit only applies if\nchar\n>> > parsestring[] is used, not if char *parsestring is used. This is the\nwhole\n>> > reason for using flex. And scan.l is set up to compile using char\n>> > *parsestrin... |
[
{
"msg_contents": "I attach the patch for Statement Triggers (StmtTrig) in postgreSQL.\nStatement Triggers are executed only once for the command use in the\ndefinition not influenced by the number of tuples affected. With this path\nis valid the sentence\n\n \"CREATE TRIGGER disp1 BEFORE INSERT ON tbtest FOR E... |
[
{
"msg_contents": "The reason for the tag as to be able to return to the 6.5 release source\ncode. It's production code, and should be accessible at least for the next\ncouple of months.\n\nWas a tag created for 6.5.1? The object is to be able to check out any\nparticular release, bugs and all, whenever we fe... |
[
{
"msg_contents": "Yes, all that too ;-)\n>> \n>> On Wed, 25 Aug 1999, Ansley, Michael wrote:\n>> \n>> > The reason for the tag as to be able to return to the 6.5 release\nsource\n>> > code. It's production code, and should be accessible at least for the\nnext\n>> > couple of months.\n>> > \n>> > Was a tag cre... |
[
{
"msg_contents": "What I remember REL6_5 tags the version 6.5.1,\nso probably the tags should read REL6_5_0, REL6_5_1 ....\nto show that fact.\n\n> I like the frozen tag myself, since, in the future, if we need to create a\n> quick tar ball of what things looked like at that release (ie.\n> v6.5->v6.5.2 patch?... |
[
{
"msg_contents": "\nHello hackers,\n\nI'm sorry to clutter email but I've been delving into mail archives enough\nto know that a stuck spinlock is a problem but I haven't been able to\ndetermine what the solution is.\n\nI'm running postgresql 6.5 beta 1 on WindowsNT4.0 under the Cygwin\nenvironment. I've actu... |
[
{
"msg_contents": "i try to dump records out , just two colums using\n\npsql emq_frontend -c \"select 1column,2column from table;\">twocolumnsout\n\nfrom a 1.2 mill db\n\nand it gives me either out of memory\nor backend close or\nsent d b4 t errors\nalso a setallocmem()\nsorry for psuedo quoting\n\nhas anyone e... |
[
{
"msg_contents": "This is three files IMHO useful for community\n\n1. SysV start script for postgres, also can be used under freebsd\n (see below)\n2. simple utility su_postgres, it make su to user postgres whether or not\n shell for it specified, is better than su for security reason \n3. configure/confi... |
[
{
"msg_contents": "I have written a program to convert HTML to troff, so I am attaching a\nPDF version of our FAQ.\n\nThe output looks pretty good, and required no hand-tuning.\n\n-- \n Bruce Momjian | http://www.op.net/~candle\n maillist@candle.pha.pa.us | (610) 853-3000\n... |
[
{
"msg_contents": "PGSQL 6.5.0, FreeBSD 3.2, Intel Pentium II 366MHz, 128 MB\n\nThe table below was filled with about 1,000,000 records. Then a bunch of\nindexes was created and a VACUUM executed.\n\nI was under impression that when max(<primary key>) is called, it should\njust take the value from the index. I ... |
[
{
"msg_contents": "I posted this message in pgsql-novice, but got no answer.\nI dare forward it to pgsql-hackers, though I fear it could be a misuse\nof that list.\n\nCould you post an answer on novice since I've not subscribed to hackers.\n(Too high level for me, I think)\n\nSpirou wrote:\n> \n> I can't find m... |
[
{
"msg_contents": "The syntax needed for defining functions is quite annoying because of the\nneeded quoting. Example:\n\nCREATE FUNCTION bla (int4) RETURNS char AS '\n BEGIN\n RETURN ''Two quotes needed''\n END;\n' LANGUAGE 'plpgsql';\n\nHow about allowing something like in shell h... |
[
{
"msg_contents": "The syntax needed for defining functions is quite annoying because of the\nneeded quoting. Example:\n\nCREATE FUNCTION bla (int4) RETURNS char AS '\n BEGIN\n RETURN ''Two quotes needed''\n END;\n' LANGUAGE 'plpgsql';\n \nHow about allowing something like in... |
[
{
"msg_contents": "Hi.\n\nThe entries entered in pg_shadow haven't ever worked for me. I've tried a\nnumber of times without success. If I update a user in there and set a\npassword for them:\npostgres=> select * from pg_shadow;\nusename |usesysid|usecreatedb|usetrace|usesuper|usecatupd|passwd|valuntil ... |
[
{
"msg_contents": "Hello all,\n\ntrying the new version of PgAccess (hope tomorrow will be available) I\ndiscovered that clustering a table on an index loose also the NOT NULL\nattributes from the original table. I know that the permissions are also\nlost but didn't read anywhere about the NOT NULL.\n\nBest reg... |
[
{
"msg_contents": "Hello,\n\nis there any rough estimate of when Postgres ANSI SQL compliance\nis planned to be implemented? Will it be in 6.6, 6.7, or later?\nAny info would be appreciated.\n\nNejc\n\n-- \n''Share and Enjoy.''\n\n",
"msg_date": "Sun, 29 Aug 1999 14:43:16 +0200",
"msg_from": "Jernej Zaj... |
[
{
"msg_contents": "Are we going to release 6.5.2? If yes, then when?\n---\nTatsuo Ishii\n",
"msg_date": "Sun, 29 Aug 1999 21:45:24 +0900",
"msg_from": "Tatsuo Ishii <t-ishii@sra.co.jp>",
"msg_from_op": true,
"msg_subject": "PostgreSQL 6.5.2"
},
{
"msg_contents": "Tatsuo Ishii <t-ishii@sr... |
[
{
"msg_contents": "For some reason we currently support sub-SELECT expressions only\nin WHERE and HAVING clauses, not in the target list of a SELECT.\nDoes anyone know why this is?\n\nThere are a number of places in the planner/optimizer that would need\nto be fixed to make it happen, but the changes are utterl... |
[
{
"msg_contents": "Hello,\n\nI have a very big table (valori) with the following columns:\n- data datetime\n- debitor float8\n- creditor float8\n\nIt has a btree index on data (non unique).\n\nThe following select is using the index:\n\nselect * from valori where data > '25-10-1999'\n\nNOTICE: QUERY PLAN:\nInd... |
[
{
"msg_contents": "\n> I posted this message in pgsql-novice, but got no answer.\n> I dare forward it to pgsql-hackers, though I fear it could be a misuse\n> of that list.\n> \nI think it is a good question for the hackers list.\n\n> Spirou wrote:\n> > \n> > I can't find my classes anymore (cf below ...) !\n> \... |
[
{
"msg_contents": "Hi,\n\nplease add the file ipc.patch (patch for the cygipc library) into src/win32\ndirectory and apply the patch for README.NT (readme.patch). I think it\nshould go into both the 6.5.2 and current trees.\n\nI have no reaction from the author of the cygipc library yet, so it will be\nbetter t... |
[
{
"msg_contents": "Hi Denny,\n\nI solved this problem (backend crashes when we delete a group without\nrevoking privileges) adding the group again with the same grosysid, revoking\nall privileges on all tables and deleting this group.\n\nBest Regards,\n\nRicardo Coelho.\n\n----- Original Message -----\nFrom: D ... |
[
{
"msg_contents": "\ngrowing tired of the ever increasing \"User Unknown\" or \"Host Unreachable\"\nmessages, I've implemented 'bouncefilter2' on the majordomo lists, which\nacts as a sort of 'inbetween' agent to catch, record and act on these\nDSNs...\n\nThe goal is to reduce the overall processing required, a... |
[
{
"msg_contents": "> and why not something like:\n>\n> CREATE FUNCTION first_word ( :x CHAR VARYING(1000) )\n> RETURNS CHAR VARYING(40)\n> LANGUAGE SQL\n> RETURN TRIM (SUBSTRING ((:X || ' ') FROM 1 FOR POSITION (' ' IN (:X || '')\n> )));\n>\n> as described in SQL/PSM (SQL Persistent Stored Modules) (se... |
[
{
"msg_contents": "I have had a request to add multi-byte support to the Debian binary\npackages of PostgreSQL.\n\nSince I live in England, I have personally no need of this and therefore\nhave little understanding of the implications.\n\nIf I change the packages to use multi-byte support, (UNICODE (UTF-8) is\n... |
[
{
"msg_contents": "Has anyone seen a problem with postgresql-6.5.1 leaking file descriptors? I\nam not sure what exact activity causes the problem, but e.g. using pgaccess\nto inspect the database causes the following:\n\ncr@photox% ps ax|grep postgres\n 425 ?? Ss 1:58.01 /usr/local/pgsql/bin/postmaster... |
[
{
"msg_contents": "Has anyone seen a problem with postgresql-6.5.1 leaking file descriptors? I\nam not sure what exact activity causes the problem, but e.g. using pgaccess\nto inspect the database causes the following:\n\ncr@photox% ps ax|grep postgres\n 425 ?? Ss 1:58.01 /usr/local/pgsql/bin/postmaster... |
[
{
"msg_contents": "> Modified Files:\n> parse_node.h parse_oper.h\n> Remove bogus code in oper_exact --- if it didn't find an exact\n> match then it tried for a self-commutative operator with the reversed input\n> data types. This is pretty silly; there could never be such an operator,\n> except maybe ... |
[
{
"msg_contents": "Hi,\n\nDaniel Horak wrote:\n\n> Hi,\n> \n> please add the file ipc.patch (patch for the cygipc library) into src/win32\n> directory and apply the patch for README.NT (readme.patch). I think it\n> should go into both the 6.5.2 and current trees.\n> \n> I have no reaction from the author of the... |
[
{
"msg_contents": "Just a month ago, we posted a bug-report on the BUGS mailing list\nconcerning the optimizer plan enumeration in the 6.5.0 release.\nWe haven't seen any comment about it and the problem is still unfixed in\nthe last release, so we wish to have a feedback from someone of the\ndevelopers.\nWe al... |
[
{
"msg_contents": "Leon took it out with a patch that he sent in about ten days ago. I did\nsome (very) basic testing, and it seemed to remove the problem of limiting\nthe token size, which is what I was after.\n\nMikeA\n\n>> -----Original Message-----\n>> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]\n>> Sent: Tu... |
[
{
"msg_contents": "I'll send it to you first thing in the morning. I'm afraid I'm not\nconnected at home. I've got a good scan.l, although I haven't touched\ngram.y.\n\n>> -----Original Message-----\n>> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]\n>> Sent: Tuesday, August 31, 1999 4:15 PM\n>> To: Ansley, Michae... |
[
{
"msg_contents": "Hi, \n\nI just compiled and installed Postgres 6.5.1 on Slackware 4.0 (kernel 2.2.6,\ncpu: PIII@450) whithout changing anything on the code. The regression tests had\nsome strange failures, so i'm sending you the .out and .diff files.\n\nThanks for your efforts on Postgres,\n\nT.\n\n-- \nTheo... |
[
{
"msg_contents": "Hi,\n\nthere is a bug in my array contrib. The varchar and bpchar function don't\nwork correctly. The following patch (for 6.5.1) fixes the problem.\n\n*** contrib/array/array_iterator.c.orig\tSat Jun 5 21:09:35 1999\n--- contrib/array/array_iterator.c\tTue Aug 31 11:22:44 1999\n************... |
[
{
"msg_contents": "> I think we ought to hold up 6.5.2 long enough to cram this patch in, but\n> I'm hesitant to stick it in the stable branch without some more testing.\n> Cyrus, can you try it and see if it fixes your problem?\n\nOk, I can't actually try the patch for another week or so, since my\ndevelopment... |
[
{
"msg_contents": "Anyone run into this error before:\n\nERROR: Unable to locate type oid 718 in catalog\n\nThis occurred when I tried to 'vacuum verbose analyze' my database. The\nlast time it occurred, I had to re-build the database to get rid of the\nerror message. Perhaps the pg_catalog is getting corrupte... |
[
{
"msg_contents": "subscribe\n\n\n",
"msg_date": "Tue, 31 Aug 1999 20:30:00 +0200",
"msg_from": "fjcuberos@rtva.es",
"msg_from_op": true,
"msg_subject": "None"
}
] |
[
{
"msg_contents": "Hi All,\n\nCall CVS update I'm getting:-\n\nmtcc:[/export/home/emkxp01/pgsql](39)% cvs update\nFatal error, aborting.\n: no such user\n\n\"truss\"ing the progess I can see:-\n\nsend(3, \" B E G I N A U T H R\".., 19, 0) = 19\nsend(3, \" / u s r / l o c a l / c\".., 18, 0) = 18\nsend... |
[
{
"msg_contents": "Okay, I finally convinced my partner that making a table named 'circle'\nand dropping the type 'circle' to compensate is just a bad idea. We're\ngoing to rename the table 'circles' and restore the 'circle' type. Could\nyou give me the psql command line to restore the circle type?\n\nThanks.\n... |
[
{
"msg_contents": "Is there Changes list for 6.5.2 ? I checked REL6_5 tree and didn't\nfind it. It seems that Vadim's patch for nbtinsert.c (row-reuse)\nstill didn't applied.\nThis patch prevents index file to grow indefinitely and I consider it\nas a bug fix. It's not complete, index file still grow but with ... |
[
{
"msg_contents": "Hi,\n\nwhen trying to compile the \"current\" sources under Solaris 2.5.1, \nthe yacc-generated C source in interfaces/ecpg/preproc/preproc.c \nseems to be faulty:\n\ngcc -I../../../include -I../../../backend -I/usr/local/tcltk-8.0p2/include -Wall -Wmissing-prototypes -I../include -DMAJOR_... |
[
{
"msg_contents": ">> There is the possibility for ambiguity. But it is our responsibility\n>> to minimize that ambiguity and to make a predictable system, in the\n>> presence of Postgres' unique and valuable features such as type\n>> extension. imho this is more important than, for example, allowing\n>> infini... |
[
{
"msg_contents": "I think I found some bugs in SELECT...\nI have two tables MASTER1 and DETAIL1 both of them with only one field\nCODE\nof data type VARCHAR but MASTER1.CODE is 11 char long and DETAIL1.CODE\n16 char l\n\nhygea=> \\d master1\nTable = master1\n+----------------------------------+-------------... |
[
{
"msg_contents": "Hi all,\n\nUnless it exists, I'd like to implement code for the array manipulations\nabove for Postgresql. and I need some help for it. I have already run\nthrough the sources concerned but I need to be pointed to the right\ndirection on where to start and what kind of functions I should use.... |
[
{
"msg_contents": "Also (coming late into this conversation), Array support in the JDBC2\ndriver is on the cards for 6.6.\n\nPeter\n\n-- \nPeter Mount\nEnterprise Support\nMaidstone Borough Council\nAny views stated are my own, and not those of Maidstone Borough Council.\n\n\n\n-----Original Message-----\nFrom:... |
[
{
"msg_contents": "This is a lost Vadim's patch for 6.5X tree\n\n\tOleg\n_____________________________________________________________\nOleg Bartunov, sci.researcher, hostmaster of AstroNet,\nSternberg Astronomical Institute, Moscow University (Russia)\nInternet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/\... |
[
{
"msg_contents": "Anyone looking into where these are coming from? They seem to be coming\nfrom the news server on hub for some reason.\n\n----- Forwarded message from Hub.Org News Admin -----\n",
"msg_date": "Wed, 1 Sep 1999 15:23:05 -0400 (EDT)",
"msg_from": "\"D'Arcy\" \"J.M.\" Cain <darcy@druid.ne... |
[
{
"msg_contents": "Hiroshi spotted the fundamental problem we were having:\nRelationFlushRelation would happily flush a relation-cache\nentry that still had an open file entry at the md.c and fd.c\nlevels. This resulted in a permanent leak of md and vfd\nfile descriptors, which was most easily observable as a ... |
[
{
"msg_contents": "Hi,\n\nI got a email from Russia with commercial questions.\nUnfortunately it's written in russian. Whom I should forward\nthis message ?\n\n\tRegards,\n\n\t\tOleg\n\n_____________________________________________________________\nOleg Bartunov, sci.researcher, hostmaster of AstroNet,\nSternbe... |
[
{
"msg_contents": ">> > To my mind, without spaces this construction *is* ambiguous, and\nfrankly\n>> > I'd have expected the second interpretation ('+-' is a single operator\n>> > name). Almost every computer language in the world uses \"greedy\"\n>> > tokenization where the next token is the longest series o... |
[
{
"msg_contents": "Your database url is wrong. A postgres database needs the following URL:\njdbc:postgresql://theComputerName/thePostgresDatabaseName\nif you omit something, you get your NullPointerException\n\nChristian\n\nEA wrote:\n> \n> Here are the errors I get while running the example classes provided b... |
[
{
"msg_contents": "\nMorning all...\n\n\tAm looking at a v6.4 system, and if I do:\n\nselect relname from pg_class;\n\n\tIt returns all the relations...but if I do:\n\nselect relname,relacl from pg_class;\n\n\tIt gives me:\n\npqReadData() -- backend closed the channel unexpectedly.\n This probably means ... |
[
{
"msg_contents": "Hi, Ive spent the last 4 days working my butt off trying to find the cause of\nthe seemingly random vacuum analyze crash. Actually Ive been just\ntrying to reproduce it, cos as soon as I added in -ggdb into the\ncompile rules it stopped happening *grrr* (not that Im surprised. It\nwas random... |
[
{
"msg_contents": "Sorry, guys. Here is the ultimate patch which keeps the entire\nbehavior as it was, apart from forbidding minus-terminated \noperators. Seems that I have to break the habit of doing before\nthinking properly :-/ The point is that my second patch breaks\nconstructs like a & b or a ! b. Thi... |
[
{
"msg_contents": "[Charset iso-8859-1 unsupported, filtering to ASCII...]\n> Bruce,\n> \n> The replacement of the existing client/server communication project with\n> CORBA looks very interesting, I would love to get involved with something\n> like that. Is there anyone working on it at the moment? What area o... |
[
{
"msg_contents": "> This inconsistency bothers me: I've always thought that char(),\n> varchar(), and text() are functionally interchangeable, but it seems\n> that's not so. Is this behavior mandated by SQL92?\n\nYes, the behavior is correct, and mandated by SQL92. \nA char would not be able to hold the infor... |
[
{
"msg_contents": ">> \n>> No good: we already have some. There are three standard geometric\n>> operators named \"?-\" ... not to mention lord-knows-what user-defined\n\t<snip>\n>> It would also be worth remembering that \"-\" is far from the \n>> only unary\n>> operator name we have, and so a solution that c... |
[
{
"msg_contents": "Leon wrote:\n>> Ok. Especially if there are more unary operators (I always wondered\n>> what unary % in gram.y stands for :) it is reasonable not to make\n>> a special case of uminus and slightly change the old behavior. That\n>> is even more convincing that constructs like 3+-2 and 3+-b wer... |
[
{
"msg_contents": "> But if it is correct, then we need to turn off oprcanhash for bpchareq.\n> Odd that no one has noticed this before.\n\nCurrently it works for constants, because they are blank padded.\nIt does not work for the char(8) = char(16) comparison with two\ntable columns.\n\nEighter the hash functi... |
[
{
"msg_contents": "I've got trouble in a *clean* checkout of this morning's current tree.\nSomething in the system tables is not quite consistant:\n\npostgres=> \\d\nERROR: nodeRead: Bad type 0\n\nAlso, I'm getting failures in regression tests:\n\nconstraints .. failed\n>From a bunch of similar messages; relat... |
[
{
"msg_contents": ">> \"Ansley, Michael\" <Michael.Ansley@intec.co.za> writes:\n>> > I have a bit of a problem with reading this: a > -2 correctly,\n>> > while not reading this: a>-2 correctly, because that implies that you\nare\n>> > using the space as a precedence operator. This should be done by\nbraces.\n>... |
[
{
"msg_contents": "If an elog(ERROR) occurs while the reference count of a relcache entry\nis positive, there is no mechanism to set the reference count back to\nzero during abort cleanup. Result: the relcache entry has a permanent\npositive refcnt.\n\nThis has a number of bad effects, but one of the worst is ... |
[
{
"msg_contents": "Hi all again,\n\nTom, _thanks_ for information! I really appreciated it. I managed to\ncreate a function which can be used to append or delete elems in an\ninteger array. I needed it because I wanted to somehow solve the\nuser-group relationship problems with Postgres.\n\nIf you are intereste... |
[
{
"msg_contents": "I found weird behavior with temp tables.\n\ntest=> create table u1(i int);\nCREATE\ntest=> insert into u1 values(1);\nINSERT 3408201 1\ntest=> insert into u1 values(1);\nINSERT 3408202 1\ntest=> create temp table u1(i int primary key);\nNOTICE: CREATE TABLE/PRIMARY KEY will create implicit i... |
[
{
"msg_contents": ">> \n>> > Point taken. So, if the spaces are used, then a>-2 is not \n>> the same as a>-\n>> > 2. The latter should then generate an error, right?\n>> \n>> It wasn't real clear where you intended to insert whitespace in this\n>> example... but in any case, it might or might not generate an ... |
[
{
"msg_contents": "���������������������� ������������������ �������� ����������.\n���������������������� �������� ��������������������..������������ ��������������...!!\n^^",
"msg_date": "Sun, 5 Sep 1999 22:41:35 +0900 (KST)",
"msg_from": "supercd@hanmail.net",
"msg_from_op": true,
"msg_subject... |
[
{
"msg_contents": " I downloaded and built PostgreSQL on my Sparc2 running RedHat 6.0 (I've\ndone this before on my RH 6.0 x86 box). The compile/installation went fine.\nWhen the system comes up it starts the DB using the contrib/linux init\nscript.\n When I su to postgres and try to create a user or dat... |
[
{
"msg_contents": "Pursuant to a phone conversation I had with Bruce, I added code this\nmorning to reject DROP TABLE or DROP INDEX inside a transaction block;\nthat is, you can't do BEGIN; DROP TABLE foo; END anymore. The reason\nfor rejecting this case is that we do the wrong thing if the transaction\nis lat... |
[
{
"msg_contents": "This is a warning an a request for change in pg_dumpall behaviour.\n\nOne of my co-workers accidentally used pg_dumpall instead of pg_dump \ngiving it also a dbname argument. According to man pg_dumpall:\n\n pg_dumpall takes all pg_dump options, but -f and dbname should \n not be used.\n\nt... |
[
{
"msg_contents": "\nI am using the posgresql 6.5.1.\n\nI have begin a transaction and insert a lot of tuples in the \ntransaction. The simplified code is as following:\n\n----------------------------------\n res = PQexec(conn,\"BEGIN\");\n PQclear(res);\n\n PQexec(conn, \"INSERT INTO qms_table (idr1, idr2, ... |
[
{
"msg_contents": ">> In short, a lot of work for a very marginal feature. How many other\n>> DBMSes permit DROP TABLE to be rolled back? How many users care?\n>\n> Oracle auto-commits current in-progress transaction before\n> execution of any DDL statement and executes such statements in\n> separate transact... |
[
{
"msg_contents": "Thanks a lot for your explanations.\nWe have started working with the snapshot and have found a problem with\nthe selectivity estimation of join clauses, probably you just know of\nthis.\nWhen the join is between attnos < 0 (such as oids), the selectivity is\nestimated as 0.5 (leading to very... |
[
{
"msg_contents": "\nThis is an error I am getting with 6.3.2\nunder freebsd 2.2.8\nMon Sep 6 16:44:48 BST 1999: NOTICE: SIAssignBackendId: discarding tag 2147483020\nMon Sep 6 16:44:48 BST 1999: FATAL 1: Backend cache invalidation initialization failed\n\n\nOur database is about 38megabyes. We do have about 20... |
[
{
"msg_contents": "I know Tom Lane has done some work on pg_upgrade -- the last message was\non 8/2/99, and left the thread hanging.\n\nWhat is the current status of pg_upgrade in 6.5.x??\n\nI ask because the presence of a working pg_upgrade drastically reduces\nthe work necessary to get postgresql upgrading wo... |
[
{
"msg_contents": "I have configured, built, and installed ProsgreSQL 6.5.1 using:\n\n --with-tcl and --with-tkconfig=<dir>\n\nAs far as I have looked, everything was built and installed without a\nhitch. The pltcl library is in the right location, and /etc/ld.so.conf\nlists that directory.\n\nWhen I define ... |
[
{
"msg_contents": "Hi\n\nOkee, I have caught the vacuum analyse crash that was giving me a load of\ngrief\n\nFirstly, I create the following database\n\n$psql crashtest\nWelcome to the POSTGRESQL interactive sql monitor:\n Please read the file COPYRIGHT for copyright terms of POSTGRESQL\n[PostgreSQL 6.5.1 on i... |
[
{
"msg_contents": " Alright, I managed to find out why PostgreSQL dies when run on my Sparc.\nSeems it's hitting a function called tas() and never exiting (that's what\ngdb postmaster <id> is showing from the backtrace anyway). I've managed to\nfind about three or so different places where tas() is defined ... |
[
{
"msg_contents": "Hi !\n\nI would like to know our I can read the log file.\n\nIs it the file where I can detail all the transactions ?\n\nRegards,\n\nStephane FILLON\n\n\n\n\n\n\n\nHi !\n \nI would like to know our I can read the log \nfile.\n \nIs it the file where I can detail all the \ntransactions ?\n \nR... |
[
{
"msg_contents": "> Cope with versions of vsnprintf() written by people who\n> don't read man pages...\n\nRETURN VALUE\n If the output was truncated, the return value is -1,\n otherwise it is the number of characters stored, not\n including the terminating null.\n\nIs this consistant wi... |
[
{
"msg_contents": "Hi All, \n\nI just tried to get pgindent to work and I ran into a few snags\n\n1)\n\nI tried the src/tools/pgindent/indent.bsd.patch on two recent\nversions of bsd indent. One from the current version of openbsd, and\none from freebsd RELENG_3. In neither case the patch applied cleanly.\n\n\n... |
[
{
"msg_contents": "> I am physician and I am very interested by possibilities postgresql\n> could offer to medical information management, specially in undeveloped\n> countries.\n> In the userguide you speake about a medical database and I would want to\n> contact people responsable of this project.\n\nI believ... |
[
{
"msg_contents": "Ummmm\n\nOkee, this may be my setup being weird. I have been working on that\nvacuum analyze bug and that may have killed something in the pg tables.\n\nHowever, I am slightly concerned about this.\n\nI am using 6.5.2 beta (the tarball on the ftp site)\n\n-----------------------------\n\n$ cr... |
[
{
"msg_contents": "Following case statement is legal but fails in 6.5.1.\n\ndrop table t1;\nDROP\ncreate table t1(i int);\nCREATE\ninsert into t1 values(-1);\nINSERT 4047465 1\ninsert into t1 values(0);\nINSERT 4047466 1\ninsert into t1 values(1);\nINSERT 4047467 1\n\nselect i,\n case\n when i < 0 then 'min... |
[
{
"msg_contents": "Michael Simms was kind enough to give me login privileges on his system\nto poke at his problems with vacuum running concurrently with table\ncreate/drop operations. I am not sure why his setup seems to display\nthe problem easier than mine does, but it's certainly true that crashes\noccur v... |
[
{
"msg_contents": "I have finished applying Mike Ansley's changes for long queries, along\nwith a bunch of my own. The current status is:\n\n* You can send a query string of indefinite length to the backend.\n (This is poorly tested for MULTIBYTE, though; would someone who\n uses MULTIBYTE more than I do try... |
[
{
"msg_contents": "Hi,\n\nSorry for the intrusion, but the www-based bug tracking seems to be down\n(URL not found by the www server).\nMy problem: I'm testing 6.5.1 on a Linux (old RedHat 4.2,libc5) box.\nI did the regression tests, and int2 ant int4 failed, but int8 was ok.\nBut this is the minor problem, may... |
[
{
"msg_contents": "\nBefore I dive into this, has anyone else noticed that the SRCH_INC and\nSRCH_LIB options in the templates no longer work?\n\nTo test, I modified template/freebsd as follows:\n\nAROPT:cq\nSHARED_LIB:-fpic -DPIC\nCFLAGS:-O2 -m486 -pipe\nSRCH_INC:/usr/local/include\nSRCH_LIB:\nUSE_LOCALE:no\nD... |
[
{
"msg_contents": "Do people want pgaccess updated to 0.98 for the 6.5.2 release?\n\n-- \n Bruce Momjian | http://www.op.net/~candle\n maillist@candle.pha.pa.us | (610) 853-3000\n + If your life is a hard drive, | 830 Blythe Avenue\n + Christ can be your backup. ... |
[
{
"msg_contents": "Hey hackers:\nI'vebeen using pg_dump in a typical three db setup: development,\nstaging, and live. The output of pg_dump is ordered by oid, so as the\ndb's histories diverge, the output does as well. That is, if identical\ntables get created in the development and staging dbs, for example, bu... |
[
{
"msg_contents": "\n\nCalling setBytes or any attempt to do LargeObject.write(byte[])\nreturns\n\n[on the java side]\nOid gotten from lom.create() is 641377\nFastPath call returned ERROR: lo_write: invalid large obj descriptor (0)\n\n at postgresql.fastpath.Fastpath.fastpath(Fastpath.java:141)\n ... |
[
{
"msg_contents": "This looks like you have either not got AutoCommit set to false, or are\ncalling commit() between calls. As of 6.5.x LargeObjects need to be\nwrapped within a transaction, but if I'm right, all open LO's are closed\non commit().\n\nPeter\n\n-- \nPeter Mount\nEnterprise Support\nMaidstone Boro... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.