threads listlengths 1 2.99k |
|---|
[
{
"msg_contents": "> > > * Instantaneous crash recovery.\n> > \n> > Because this never worked reliable, Vadim is working on WAL.\n> \n> Postgres recovery is not reliable?\n\nYes. It's possible to lose indices...\nThere is paper how to avoid this, somewhere in Berkeley' site.\nAs I remember, additional TID ... |
[
{
"msg_contents": "> > > Do you mean way back when it was removed? How was it \n> getting in the way?\n> > \n> > Yes. Every tuple had this time-thing that had to be tested. Vadim\n> > wanted to revove it to clear up the coding, and we all agreed.\n> \n> And did that save a lot of code?\n\nThis removed one fsy... |
[
{
"msg_contents": "> > * It's always faster than WAL in the presence of stable main memory.\n> > (Whether the stable caches in modern disk drives is an \n> > approximation I don't know).\n> \n> Yes, only if you want to be able to log changes to a txlog to \n> be able to rollforward changes after a restore, then... |
[
{
"msg_contents": "Welcome 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 \\g or terminate with semicolon to execute query\n \\q to quit\n\ntest=# create table pg_test... |
[
{
"msg_contents": "Well, I took Thomas' advice and upgraded to 7.0.2 from source.tar.gz. \n\nFor some reason, I cannot create the following index:\n\ndb_geocrawler=# DROP INDEX idx_mail_archive_list_subject;\nERROR: index \"idx_mail_archive_list_subject\" nonexistent\n\ndb_geocrawler=# CREATE INDEX \"idx_mail... |
[
{
"msg_contents": "Okay, the crowd seemed to say that PostgreSQL is not really harder to\ninstall than MySQL, but that it isn't easy either. My personal goal then\nis to make the installation so easy that even people who don't even have\nany data will download and install PostgreSQL just to see how smooth it\nw... |
[
{
"msg_contents": "Theoretically, the documentation should be installed automatically when\nyou do `make install'. Users shouldn't have to look for it separately.\n\nThat's of course a problem: the CVS source doesn't contain any\ndocumentation and most people are not set up to rebuild it. Ignoring\nmissing file... |
[
{
"msg_contents": "I know you're all sick of hearing from me, but I'm passing this along\nanyway. Looks like I need to go back down to 6.5.3 for some reason.\n\nThe following query is at the very heart of the site and it takes\nupwards of 15-20 seconds to run now. It used to be instantaneous.\n\nexplain SELECT ... |
[
{
"msg_contents": "I suggest that we change vacuum to only move remove tuples if there is\nmore than 20% expired tuples.\n\nWhen we do vacuum, we drop all indexes and recreate them. \n\nThis fixes the complaint about vacuum slowness when there are many\nexpired rows in the table. We know this is causes by exc... |
[
{
"msg_contents": "On Tue, 11 Jul 2000, Alfred Perlstein wrote:\n> In an effort to complicate the postmaster beyond recognition I'm\n> proposing an idea that I hope can be useful to the developers.\n \n> Connection pooling:\n \n> The idea is to have the postmaster multiplex and do hand-offs of\n> database conne... |
[
{
"msg_contents": "While testing the just-committed executor memory leak fixes, I observe\nthat there are still slow leaks in some operations such as sorts on\nlarge text fields. With a little digging, it seems that the leak must\nbe blamed on the behavior of aset.c for large chunks. Chunks between\n1K and 64... |
[
{
"msg_contents": "\n> > I don't like that --- seems it would put a definite crimp in the\n> > whole point of TOAST, which is not to have arbitrary limits on field\n> > sizes.\n> \n> If we can solve it, let's do so. If we cannot, let's restrict\n> it for 7.1.\n\nHow are you doing the index toasting curr... |
[
{
"msg_contents": "Although it sounds like a good idea, over the years I've not seen a split\nreally work well unless there is a real divide between them.\n\nLike our Hackers & Interfaces lists now, they are quite different, but some\nproblems relating to say JDBC also affect ODBC, and soon people start cross\n... |
[
{
"msg_contents": "\n> Philip's INSERT ... RETURNING idea could support returning TID and\n> table OID as a special case, and it has the saving grace that it\n> won't affect apps that don't use it...\n\nYes, and the current fe-be protocol can handle it, since an on insert rule\ncan also return a select result f... |
[
{
"msg_contents": "\nI have been speaking to Pavel about pg_dump support of blobs, and he thinks\nit is important to allow for some kind of human-readable version of the\ndump to be created.\n\nMy guess is that this will involve a plain text schema dump, followed by\nall BLOBs in separate files, and a script to... |
[
{
"msg_contents": "Slashdot has a report about Interbase and their new Kilyx development\nenvironment.\n\n\thttp://slashdot.org/articles/00/07/12/124244.shtml\n\n-- \n Bruce Momjian | http://candle.pha.pa.us\n pgman@candle.pha.pa.us | (610) 853-3000\n + If your life is... |
[
{
"msg_contents": "Why not have it using something like tar, and the first file being stored in\nascii?\n\nThat way, you could extract easily the human readable SQL but still pipe the\nblobs to stdout.\n\nPeter\n\n--\nPeter Mount\nEnterprise Support\nMaidstone Borough Council\nAny views stated are my own, and n... |
[
{
"msg_contents": "At 14:58 12/07/00 +0100, Peter Mount wrote:\n>Why not have it using something like tar, and the first file being stored in\n>ascii?\n>\n>That way, you could extract easily the human readable SQL but still pipe the\n>blobs to stdout.\n\nHas Tom Lane paid you to send this message? :-}\n\nIf any... |
[
{
"msg_contents": "No he didn't, just I've been sort of lurking on this subject ;-)\n\nActually, tar files are simply a small header, followed by the file's\ncontents. To add another file, you simply write another header, and contents\n(which is why you can cat two tar files together and get a working file).\n\... |
[
{
"msg_contents": "\n> The actual behaviour of the toaster is to toast each tuple\n> until it has a delicious looking, brown and crispy surface.\n> The indicator for beeing delicious is that it shrank below\n> MaxTupleSize/4 - that's a little less than 2K in a default 8K\n> blocksize... |
[
{
"msg_contents": "Which is why having them on stdout is still a nice option to have. You can\npipe the lot through your favourite compressor (gzip, bzip2 etc) and\nstraight on to tape, or whatever.\n\nI don't know why you would want them as separate files - just think what\nwould happen to directory search tim... |
[
{
"msg_contents": "At 15:32 12/07/00 +0100, Peter Mount wrote:\n>Which is why having them on stdout is still a nice option to have. You can\n>pipe the lot through your favourite compressor (gzip, bzip2 etc) and\n>straight on to tape, or whatever.\n\nWell, the custom format does that, it also does compression an... |
[
{
"msg_contents": "> > Just wanted to give a short message, that current snapshot does not \n> > compile on AIX due to the fmgr changes.\n> \n> Without more details, that's completely unhelpful.\n\nYes sorry, I just wanted to know if somebody already knows, \nor is working on it, before going into detail.\n\nxl... |
[
{
"msg_contents": "\n> Yes it is a multi-key index, and the matches are exact.\n> \n> Someone else asked why I have separated these fields out from the\n> mail_date.\n> \n> If I didn't, and I wanted to see the messages for this month, I'd have\n> to regex and that would overwhelm the database.\n\nAs I said in t... |
[
{
"msg_contents": "\n> Note that I don't talk about overwriting/non-overwriting smgr at all!\n> It's not issue. There are no problems with keeping dead \n> tuples in files\n> as long as required. When I told about new smgr I meant \n> ability to re-use\n> space without vacuum and store > 1 tables per file.\n> B... |
[
{
"msg_contents": "\n> >> We can't \"drop and recreate\" without a solution to the relation\n> >> versioning issue (unless you are prepared to accept a nonfunctional\n> >> database after a failure partway through index rebuild on a system\n> >> table). I think we should do this, but it's not all that simple...... |
[
{
"msg_contents": "\n> Your ideas for selecting based on the date are intriguing, however the\n> schema of the db was not done with that in mind. Everyone thinks I'm a\n> nut when I say this, but the date is stored in a char(14) field in\n> gregorian format: 19990101125959\n\nPerfect, that makes it a lot easier... |
[
{
"msg_contents": "\nI have a bunch of these just sitting there:\n\npgsql 86144 0.0 0.0 304 120 p3 D+ 5:17PM 0:00.00 grep udmsearch\npgsql 69312 0.0 3.6 21652 18808 p1 S 12:20PM 10:09.68 postmaster: /pgsql/bin/postgres pgsql 216.126.84.1 udmsearch /pgsql/bin/postgres pgsql 216.126.84.1 udmse... |
[
{
"msg_contents": "\nIgnore me ...\n\n\nMarc G. Fournier ICQ#7615664 IRC Nick: Scrappy\nSystems Administrator @ hub.org \nprimary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org \n\n",
"msg_date": "Wed, 12 Jul 2000 18:47:29 -0300 (ADT)",
"msg_from":... |
[
{
"msg_contents": "I posted this to pg_admin yesterday, but I'm not sure if anyone is\nreading that list.\n---------------------------------------------------------\n\nI have Postgres 7.0.2 installed on my RedHat Linux 6.0 system, but\nrealized today that I hadn't built any of the manual pages or\ndocumentation... |
[
{
"msg_contents": "There are quite a number of misfeatures in Postgres' current support for\naggregate functions (COUNT, SUM, etc). We've had previous discussion\nthreads about them in the past, see pghackers around 1/23/00 and 6/16/99\nfor example. I propose to fix a few things for 7.1:\n\n* Hard-wired bound... |
[
{
"msg_contents": "One thing that occurred to me, if I'm going to rejuggle the templates, why\nnot name them like the Makefile.${os} and the include/port/${os}.h? We\ndon't really need two matching logics and no matter how smart we make the\ntemplate matching, there's still nothing to be gained if we don't find... |
[
{
"msg_contents": "\nOdd .. why is heap reporting 5899, when count() only reports 2951?\n\nglobalmatch=# select count(gid) from images;\n count \n-------\n 2951\n(1 row)\n\nglobalmatch=# create index images_gid on images using btree ( gid );\nCREATE\nglobalmatch=# vacuum verbose analyze images;\nNOTICE: --Rel... |
[
{
"msg_contents": "I added the suggested index and changed my sql and the subjective tests\nseem to be improved somewhat. I checked EXPLAIN and it is using the new\nindex.\n\nI still think there must be sorting going on, as the result is returned\ninstantly if you remove the ORDER BY. I don't know - I do think ... |
[
{
"msg_contents": "Here is a great article about the Unix philosophy of doing things:\n\n http://www.performancecomputing.com/archives/articles/1998/september/9809of1.shtml\n\n-- \n Bruce Momjian | http://candle.pha.pa.us\n pgman@candle.pha.pa.us | (610) 853-3000\n + I... |
[
{
"msg_contents": "\nAfter going through the udmsearch indexer code again, I found that they\nwere doing a 'BEGIN WORK;LOCK url', but they never UNLOCKED it afterwards,\nso it was staying locked until indexer ended, several hours later ...\n\nI've fixed that code locally and sent them a patch ... problem fixed ... |
[
{
"msg_contents": "[ Charset ISO-8859-1 unsupported, converting... ]\n> Bruce,\n> \n> The bug list includes the following:\n> \n> a.. SELECT foo UNION SELECT foo is incorrectly simplified to SELECT foo \n> \n> Wy is this simplification incorrect? I don't get it.\n\nNot sure. Maybe someone can comment. \n\n--... |
[
{
"msg_contents": "\n> > The bug list includes the following:\n> > \n> > a.. SELECT foo UNION SELECT foo is incorrectly simplified \n> to SELECT foo \n> > \n> > Wy is this simplification incorrect? I don't get it.\n> \n> Not sure. Maybe someone can comment. \n\nIt can only be simplified to:\n\tSELECT DISTINCT... |
[
{
"msg_contents": "\n> I still think there must be sorting going on, as the result \n> is returned\n> instantly if you remove the ORDER BY. I don't know - I do think it's\n> much better now.\n\nAre you doing the exact query I wrote for you ?\nThat is:\n\torder by mail_list desc, mail_date desc\n\nexplain should... |
[
{
"msg_contents": "\nTom, and others...\n\nI've made modifications to libpq to accept multiple return type groups,\nand now the thing to do is to make the back-end generate them from OO\nhierarchies. Do you have any thoughts on the general approach to do\nthis? Should I be doing something like expandAll in pars... |
[
{
"msg_contents": "\nWhile working with alter table add constraint, I realized we \nget these messages if a second session blocks on the lock the \nalter table is getting. I'm not sure what (if any) way there\nis around this in the code, but I figure I should remove this\nproblem before sending the next patch ... |
[
{
"msg_contents": "\n> I went at it in a different way: pulled out pg_lzcompress into a\n> standalone source program that could also call zlib. \n\nIf you want you could give minilzo a try.\n\nLZO is a data compression library which is suitable for data de-/compression\nin real-time.\nLZO implements the fastest... |
[
{
"msg_contents": "\n> > LZO and the LZO algorithms and implementations are distributed under the\n> > terms of the GNU General Public License (GPL) { auf Deutsch }.\n> \n> GPL is alone a fatal objection for something that has to go into the\n> guts of Postgres.\n\nYes, but the author states that special projec... |
[
{
"msg_contents": "[Forwarded to PostgreSQL hackers list]\n\nFrom: for email <victor_v@permonline.ru>\nSubject: A postgreSQL question\nDate: Tue, 11 Jul 2000 00:56:35 +0600\n\n> Warning! The reply address of previous same message is bad. Please\n> use this address. \n> \n> ishii@postgresql.org\n> \n> Hello Tats... |
[
{
"msg_contents": "I have a question about performance issues related to temporary tables.\n\nIIRC temporary tables were implemented as ordinary tables with some \npre/post-processing to give them unique names so that they would not \nclash with similar-named tables from other sessions. \n\nIs this all that is ... |
[
{
"msg_contents": "Zeugswetter Andreas SB wrote:\n> \n> > IMHO temporary tables could be made significantly faster than \"ordinary\"\n> > as they are only accessed inside one session and thus have no need for\n> > locking or even WAL as they could do with max 2 copies of the same row\n> > the other of which can... |
[
{
"msg_contents": "\n> So you are not saying that INSERT on temp tables is any slower than\n> ordinary tables, just that you think there is a way to make temp tables\n> faster. \n> \n> My guess is that WAL is going to make INSERT's poor performance a\n> non-issue.\n\nI do not think that WAL in its first version... |
[
{
"msg_contents": "I see the following symptom using current sources...\n\n -Thomas\n\nmyst> psql\npsql: pqReadData() -- backend closed the channel unexpectedly.\n This probably means the backend terminated abnormally\n before or while processing the request.\nmyst> cre... |
[
{
"msg_contents": "I've committed some changes which implement a few new things.\n\n From the CVS log:\n\nImplement nested block comments in the backend and in psql.\n Include updates for the comment.sql regression test.\nImplement SET SESSION CHARACTERISTICS and SET DefaultXactIsoLevel.\nImplement SET SESSION ... |
[
{
"msg_contents": "I have been cleaning up the index-related code a little bit while\ntrying to eliminate memory leaks associated with functional indexes,\nand I have noticed an old \"feature\" that I think we should remove.\nIt's undocumented (I'd never even heard of it before) and as far as\nI can tell the on... |
[
{
"msg_contents": "Hi All,\n\nI have a five table join that should return 1 record but, 0 comes back\nthis was working before running vacuum last night - as a simple test\nI set enable_seqscan=off and hay-presstoe it came back !\n\nI guess there is an optimizer problem, so I have two questions\n\n1) Is there so... |
[
{
"msg_contents": "Here's a patch to clean up some issues with the schema diagram\neditor in pgaccess. This patch:\n\n\t* allows schema window to be resized up to full screen size\n\t* autosizes window on schema open\n\t* allows multiselect of tables (by shift click) to allow\n\t\tdragging of sets of tables\n\t... |
[
{
"msg_contents": "Hi All,\n\nAttempting to build with the current CVS I'm getting the following\nerror for every file that includes config.h.\n\n\ngcc -I../../include -Wall -Wmissing-prototypes -Wmissing-declarations -g -O2 \n-Wno-error -c -o postgres.o postgres.c\nIn file included from ../../include/c.h:4... |
[
{
"msg_contents": "I take it all back.\n\nI see, from my latest update, that config.h.in has changed.\n\nI'll do a build with the *very* latest CVS and hopefully that\nwill be OK.\n\nSorry for raising the alarm too soon.\n\nKeith.\n\nKeith Parks <keith.parks@middleton-top.co.uk>\n> \n> Hi All,\n> \n> Attempting... |
[
{
"msg_contents": "> Add PATH as a type-specific token, since PATH is in SQL99\n> to support schema resource search and resolution.\n\nYou do realize this broke the geometry regress test?\n\n\t\t\tregards, tom lane\n",
"msg_date": "Fri, 14 Jul 2000 19:59:49 -0400",
"msg_from": "Tom Lane <tgl@sss.pgh.pa.... |
[
{
"msg_contents": "> How does \"Diagrams\" sound? Anyone have a better idea? The name appears\n> on a tab. The other tabs are labelled:\n\nIf one bothers to compare with them, \"Diagrams\" is what it's called in the\nMicrosoft SQL Server world. (\"Database Diagrams\" to be exact). And they can\nbe used to build... |
[
{
"msg_contents": "\nThere is a new version of pg_dump (with blob support) at:\n\n ftp://ftp.rhyme.com.au/pub/postgresql/pg_dump/blobs/\n\nThis version supports TAR output and has a few bug fixes. There are two\nversions to download:\n\n pg_dump_...CVS.tar.gz\nand\n pg_dump_...702.tar.gz\n\nwhich can be ... |
[
{
"msg_contents": "\nAnother update of the dump code; this fixes a few bugs that people without\nzlib under 7.02 would have experienced. Also, if you wish to use zlib, you\nneed to modify the Makefile to add -DHAVE_LIBZ to the CFLAGS....\n\n--- Original announcement ----\n\nThere is a new version of pg_dump (wi... |
[
{
"msg_contents": "If you configure with --enable-depend and you are using GCC then you'll\nget dependency information generated on the fly. Give it a try. Other\ncompilers can be supported if there is demand. See Makefile.global for the\ninternals.\n\n\n-- \nPeter Eisentraut Sernanders v�g 1... |
[
{
"msg_contents": "Hi,\n\nI have hacked the full-text indexing code in contrib to make it do\nkeyword indexing.\n\nIs someone willing to run an eye over it for obvious stupidities and\nthen include it into the standard tree?\n\nOliver has been including this in the Debian distribution for a while\nnow (thanks O... |
[
{
"msg_contents": "Now that I'm actually on -HACKERS, did this make it to the list?\n\nLarry \n----- Forwarded message (env-from ler) -----\n\n2 Items I noticed with PostgreSQL 7.0.2:\n\n1) the macaddr type is NOT documented in the datatypes and functions\n documentation.\n2) the manufacturer list in the m... |
[
{
"msg_contents": "\nThis question comes out of my work on pg_dump. AFAICT, the only way of\nshowing, eg, the SQL for a procedure definition (other than 'select prosrc\nfrom pg_procs, or whatever'), is to use pg_dump.\n\nThis seems strange to me, since I often want to look at a procedure within\npsql, and runni... |
[
{
"msg_contents": "JanWieck@t-online.de (Jan Wieck) writes:\n> [ pltcl's regress test is failing ]\n> Seems to suffer due to some bug. The functions use a feature\n> of the Tcl interpreter, who treates a backslash followed by a\n> newline as a whitespace that doesn't start a new command\n> ... |
[
{
"msg_contents": "I'm not sure whether my long post made it to the list, so I created\na tarball of the patch and the awk script:\n\nftp://ftp.lerctr.org/postgresql-patches/macupdate.tar.gz\n\nThis has the patch file for mac.c to update the manufacturer list with\nthe current list from IEEE and the awk script ... |
[
{
"msg_contents": "Hi,\n\n seems to me that psql thinks to know a little too much about\n quoting. I'm not able to qoute a backslash at the end of a\n line:\n\n xxx=# select 'a\\\\b\\\\\n xxx'# c';\n ?column?\n ----------\n a\\b\n c\n (1 row)\n\n ... |
[
{
"msg_contents": "> > > > I'm not sure whether my long post made it to the list, so I created\n> > > > a tarball of the patch and the awk script:\n> > > >\n> > > > ftp://ftp.lerctr.org/postgresql-patches/macupdate.tar.gz\n> > > >\n> > > > This has the patch file for mac.c to update the manufacturer list with\n... |
[
{
"msg_contents": "\nI've tried doing as much reading on the mailing lists as I can on this.\n\nThe problem lies in that I'm trying to use PostgreSQL to store HTML \ndocuments which are larger than the default tuple size of 8120 bytes. I \noriginally thought that the data type TEXT wasn't limited in size. A... |
[
{
"msg_contents": "If I understand the fundamental design of TOAST correctly, it's not\nallowed to have multiple heap tuples containing pointers to the same\nmoved-off TOAST item. For example, if one tuple has such a pointer,\nand we copy it with INSERT ... SELECT, then the new tuple has to be\nconstructed wit... |
[
{
"msg_contents": "First:\n\n1. We're compiling on AIX 4.3.3, 64-bit, using the native compiler and gmake.\n2. I'm not an AIX compiler guru :-)\n\nHistory:\n\n1. Built postgres but failed on libpgtcl, error was a number of unrecognized symbols. This happened when we linked from libpgtcl.a to libpgtcl.... |
[
{
"msg_contents": "For the last week or so I've been getting warnings like this:\n\ngcc -c -I../../../../src/include -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -g -O1 -MMD float.c -o float.o\nIn file included from float.c:58:\n/usr/include/values.h:27: warning: `MAXINT' redefined\n/usr/local/lib/gc... |
[
{
"msg_contents": "Hi all,\n\n there have been a couple of questions WRT doing untrustable\n things like file access, LDAP and the like from inside of\n triggers or functions.\n\n Tcl is a powerful language and could do all that, but the\n interpreter used in PL/Tcl is a safe one, beca... |
[
{
"msg_contents": ">>>>> \"J\" == Jan Wieck <JanWieck@t-online.de> writes:\n\nJ> there have been a couple of questions WRT doing untrustable\nJ> things like file access, LDAP and the like from inside of\nJ> triggers or functions.\n\n With PL/Ruby you can do this by giving the option --with-saf... |
[
{
"msg_contents": "I noticed my nightly vacuum process has started dying on a certain relation\nlast night. When I try to vaccum verbose it, I get the following output.\n\nI can still do \"SELECT * FROM filelist\".\n\nfilelist is a table which has 12146 rows in it, with some 15 columns. Two\nfields in approx 8-... |
[
{
"msg_contents": "> Magnus Hagander <mha@sollentuna.net> writes:\n> > I noticed my nightly vacuum process has started dying on a \n> certain relation\n> > last night. When I try to vaccum verbose it, I get the \n> following output.\n> \n> > NOTICE: FlushRelationBuffers(filelist, 310): block 0 is \n> reference... |
[
{
"msg_contents": "Hi,\n\nI was following some newsgroups and mailing lists dedicated to web authoring\nand I've found many messages where people ask for a\ncompare table between MySQL (that they are using) and PostgreSQL.\n\nThen I was looking at MySQL documentation (info format) and I've found a very\nbad pag... |
[
{
"msg_contents": "Hi,\n\nplease look at following example:\n\nCREATE TABLE picture (\nid serial not null,\ndescription text,\nfilename text);\n\nCREATE TABLE advert (\nartist text,\ncustomer text,\ntarget text)\nINHERITS (picture);\n\nCREATE TABLE work (\nid serial not null,\nadvert_id int4 not null references... |
[
{
"msg_contents": "Jan sent me a test case that produces a \"btree: failed to add item to\nthe page\" failure message. The cause is that a btree index page needs\nto be split to make room for a new index item, but the split point is\nchosen in such a way that there still isn't room for the new item on\nthe new... |
[
{
"msg_contents": "> However, I'm not sure I believe the comment anymore: it has \n> not changed since Postgres95 and I can see that quite a bit of work has\n> been done on the duplicate-key logic since then. Furthermore findsplitloc\n> itself sometimes ignores the claimed requirement: when it does the\n> spli... |
[
{
"msg_contents": "Sorry for the cross-post, but, I figured I had to do that to get this\nfile to those who need it.\n\nFor those running the 7.0.2-2 RPMset AND having the -devel subpackage\ninstalled, copy the attached file to '/usr/include/pgsql/port/linux.h',\nand change the symlink '/usr/include/pgsql/os.h'... |
[
{
"msg_contents": "http://www.newsalert.com/bin/story?StoryId=CoxpwqbWbtefuvtaXm&FQ=%22open%20source%22&Nav=na-search-&StoryTitle=%22open%2\n\nOr,\nhttp://linuxtoday.com/news_story.php3?ltsn=2000-07-18-026-06-PR-CY-SW if\nyou have a problem with the longer URL.\n\ntitle:\nPRNewswire: Open Source CRM Effort Adds... |
[
{
"msg_contents": "> 1. The PG 4.2 code used an OID appended to the key to ensure that\n> btree items are unique. This fixes the Lehman and Yao algorithm's\n> assumption of unique keys *for insertions*, since the item being\n> inserted must have an OID different from existing items even if the\n> key values ar... |
[
{
"msg_contents": "Hi Peter. I finally got a look at the \"set\" organization of the Postgres\ndocs. Looks pretty nice; there is a tradeoff between the \"monolithic\nToC\" from before and the more organized look of the \"books within a\nset\".\n\nI have no objection to using the \"set\" style (barring unforseen... |
[
{
"msg_contents": "Has anything changed in the system tables pg_proc or pg_type since 7.0.0 was\nreleased?\n\nThis morning I've seen two weird reports on Interfaces that are showing\nNullPointerExceptions occuring on internal queries to those two tables (in\ndifferent classes, one queries just pg_type the other... |
[
{
"msg_contents": "One of these is now fixed, but the other (pg_proc) I'm not sure about.\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-----Original Message-----\nFrom: Peter Mount [mailto:petermount@it.m... |
[
{
"msg_contents": "The Query Cache\n ~~~~~~~~~~~~~~~\n (excuse me, if you obtain this email twice; first I sent it with patch in \nattache, but this list has probably some limit, because email still not in\nthe list. Hmm...)\n\n Now, the patch is available at: \n\n ftp://ftp2.zf.jcu.cz/users/zakkr/pg/pg_qcac... |
[
{
"msg_contents": "\n\n Today afternoon I a little study libpython1.5 and I mean create\nnew PL language is not a problem.\n\n I a little play with it, and here is effect:\n\ntest=# CREATE FUNCTION py_test() RETURNS text AS '\ntest'# a = ''Hello '';\ntest'# b = ''PL/Python'';\ntest'# plpython.retval( a + b );\n... |
[
{
"msg_contents": "That's what I thought. Yes, it is 7.0.* releases the reports are coming\nfrom. One has been solved (they were closing the connection before using\nit), but the other one this morning, and one this afternoon are still\npuzzling...\n\nPeter\n\n--\nPeter Mount\nEnterprise Support Mushroom\nMaids... |
[
{
"msg_contents": "> > While implementing multi-key btree-s for 6.1 I found problems with\n> > duplicates handling and this is why extra logic was added. \n> > But I never was happy with this logic -:)\n> \n> Do you not like the proposal I was suggesting? I thought it \n> was pretty much what you said yourself... |
[
{
"msg_contents": "I'm trying to sort out the documentation regarding the SysV IPC settings,\nbut I better understand them myself first. :)\n\nWe use three shared-memory segments: One is for the spin locks and is of\nnegligible size (144 bytes currently). The other two I don't know, but one\nof them seems to be... |
[
{
"msg_contents": "> > > Do not add TID to key but store key anywhere in duplicate \n> > > chain and just read lefter child page while positioning index scan,\n> > > as we do right now for partial keys?\n> > \n> > > This will result in additional reads but I like it much more than\n> > > current \"logic\"...\n>... |
[
{
"msg_contents": "> > > What about unique key insertions ?\n> > \n> > We'll have to find leftmost key in this case and do what we do now.\n> >\n> \n> Currently the page contains the leftmost key is the target page of\n> insertion and is locked exclusively but it may be different in extra\n> TID implementation.... |
[
{
"msg_contents": "Any comments on my ideas on the macaddr_manuf stuff?\n\nLarry\n-- \nLarry Rosenman http://www.lerctr.org/~ler\nPhone: +1 972-414-9812 (voice) Internet: ler@lerctr.org\nUS Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749\n",
"msg_date": "Wed, 19 Jul 2000 21:1... |
[
{
"msg_contents": "Hi,\n\n Sorry about the delay in getting the bit-code to you -- it has been a\nbit busy. Attached is a tar file with the c-code for the bit functions\nand an implementation of a user-defined type on these. I hope Thomas is\nstill prepared to integrate this as a proper type into postgres.\n... |
[
{
"msg_contents": "Hi,\n\n I'm having serious problems trying to load large amounts of data\ninto the database. I have this data in binary, database compatible,\nform, but there seems no way left to upload this data except to turn it\nall back into strings (since 7.0.2 binary copy has been disabled, making\n... |
[
{
"msg_contents": "In the atache is patch with this:\n\n SET LOCALE TO <value>\n\t\tSet locale to <value>, the <value> must be correct for\n\t\tcurrent OS locale setting. \n\n SHOW LOCALE\n\t\tShow current locale setting for all categories.\n\n RESET LOCALE\n\t\tSet locale back to start-up setting.\n\n Now, pos... |
[
{
"msg_contents": "\nThere is a yet another updated version of pg_dump (with blob support) at:\n\n ftp://ftp.rhyme.com.au/pub/postgresql/pg_dump/blobs/\n\nThis version fixes issues with restores done via a direct DB connection on\ndumps that were done with the --insert flag.\n\nThere are two versions to down... |
[
{
"msg_contents": "FYI,\n\n the huge memory allocation problem of the PGLZ compressor is\n fixed. It uses a fixed, static history table, organized as a\n double linked list, now.\n\n No performance loss on small- to medium-sized attributes. But\n a win on huge (multi-MB) attributes because of ... |
[
{
"msg_contents": "Hi,\n\n up to now, TOAST would be a v7.1 show-stopper, because due to\n the upper-block btree references problem, it's not VACUUM\n safe if there's a btree index on a toastable attribute (like\n text).\n\n The only clean way to get rid of these upper-block references\n ... |
[
{
"msg_contents": "I let FreeBSD's pkg_version reinstall postgres, the bad news is it re-did the initdb,\nand now I can't access my database files in /usr/local/pgsql/data/base/ler. \n\nThe files are still there, but the system catalog doesn't point to them.\n\nIs there a way to recover this?\n\nThanks!\n\nLarr... |
[
{
"msg_contents": "Forgive me for the tacky subject, but the analogies are not far-fetched.\n\nI was just looking whether the UNSAFE_FLOATS compile-time option could\nperhaps be a run-time option, but I'm getting the feeling that it\nshouldn't be an option at all.\n\n\"Safe\" floats check after each floating po... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.