threads listlengths 1 2.99k |
|---|
[
{
"msg_contents": "\nSorry to bother you folks but...\n\nI wrote the following to message to pgsql-interfaces. I have received one\nwork around of putting an extra locked field on the table and setting and\nunsetting that but that would cause other problems. I have thought of\ncreating a locking daemon of my ow... |
[
{
"msg_contents": "I have asked this question on all of the appropriate pgsql mailing lists\nand no one has been able to help. Please, if you could, help me out with\nthis problem. Thank you.\n--\n\nI have been playing around with this for some time now to no avail. I\nhave a table info with a two-dimensional t... |
[
{
"msg_contents": "Hi.\n\nIve recently looked into porting an internal tool our company uses to\nversion 6.5 of postgresql (from 6.4.2). Unfortunately, the original author\nof this tool used items like:\n\nPGresult *res;\n...\nmyconn = res->conn;\n\nin a few spots (usually to be used to query pg_type to get st... |
[
{
"msg_contents": "I have finished removing unused #include's from *.c files. I used the\nscripts I wrote in tools/pginclude. I can't imagine anyone doing this\nmanually, though I know there was a lot of cleanup done around 6.0 in\nthis area.\n\nThe one remaining step is to make system includes use <> and pgs... |
[
{
"msg_contents": "I am done. I have attempted not to disturbe any of the config.h #if's. \nThe only one that may have been a little messed up is multi-byte, but I\nchecked every #if, so I think we will be OK.\n\n-- \n Bruce Momjian | http://www.op.net/~candle\n maillist@candle.pha.pa... |
[
{
"msg_contents": "Thanks, Tom.\n\n>> Right, the real sequence when you are changing disk layout details is\n>> \tpg_dumpall with old pg_dump and backend.\n>> \tstop postmaster\n>> \trm -rf installation\n>> \tmake install\n>> \tinitdb\n>> \tstart postmaster\n>> \tpsql <pgdumpscript.\n>> \n>> You may want to do ... |
[
{
"msg_contents": "I think the point is that you wouldn't, but the most important part is to\nget it off the wire. Let someone do that first, and then worry about what\nthe administrator can see. One would hope that your administrator is more\ntrustworthy than joe hacker out on the network.\n\n\n>> Why would ... |
[
{
"msg_contents": "I know that you can do both. It seemed from previous postings, however,\nthat there was an issue about the urgency of each, if they are actually\nseparate issues. I would have thought that the two are linked, and would be\nsolved as such.\n\nMikeA\n\n\n>> I have no idea where this misconcep... |
[
{
"msg_contents": "\n> Vadim Mikheev wrote:\n> > \n> > > The \"restore of a server\" is a main problem here, but I suggest the\n> > > following\n> > > additional backup tool, that could be used for a \"restore of a server\"\n> > > which could then be used for a rollforward and would also be a lot\n> faster\n> >... |
[
{
"msg_contents": "Why don't you adjust the ids of your system folders, such that they are\nordered properly? You should have a fixed number of system folders, so you\ncan guarantee the ids that they will receive. So make the Inbox -4. Then\nyou just order by folder id, ascending. -4 comes first, with the u... |
[
{
"msg_contents": "Sorry guys, this line:\n>> ORDER BY (if(folderid < 0) then return(abs(folderid)) else\n>> return(folderid+max(abs(MIN(folderid)))))\n\nShould have read:\nORDER BY (if(folderid < 0) then return(abs(folderid)) else\nreturn(folderid+abs(MIN(folderid))))\n\nThe max was an error.\n\nMikeA\n\n>> \n... |
[
{
"msg_contents": "Wayne Piekarski <wayne@senet.com.au> writes:\n> the other day I did a pg_dump of our 6.4.2 database and tried to load it\n> back into 6.5 - it failed with the error message:\n\n> FATAL 1: btree: failed to add item to the page\n\nIIRC this just means the tuple is too long ... btrees want to b... |
[
{
"msg_contents": "Why are our shared libs called e.g. ecpg.so and not libecpg.so ?\nThis seems strange to me, and it also complicates the link, \nsince now I cannot say -lecpg and decide whether to link static or shared\nwith the corresponding linker flag (-bnso or -brtl on AIX)\n\nAndreas \n",
"msg_date":... |
[
{
"msg_contents": "I finally found some time to make the shared library Makefile adjustments \nfor the AIX port.\n\n <<aix.patch>> \nBruce, please apply this to the REL6_5_PATCHES (and current), \nsince it would be cool for 6.5.1.\n\nirix5 is broken, cause it has an extra _ in there. Fix is in the Patch.\n\nAnd... |
[
{
"msg_contents": "Thomas wrote:\n> > Why are our shared libs called e.g. ecpg.so and not libecpg.so ?\n> \n> Uh, they aren't on at least some platforms. Here is the lib directory\n> on my linux box:\n> \nSorry Bruce, please can you make that change to my patch:\n\n- shlib\t\t\t\t:= $(NAME)$(DLSUFFIX)\n\n+ ... |
[
{
"msg_contents": "\n> > Why are our shared libs called e.g. ecpg.so and not libecpg.so ?\n> \n> Uh, they aren't on at least some platforms. Here is the lib directory\n> on my linux box:\n> \nOk, sorry I see the difference now. Those that are for linking are named\nlib*.so\nand those that are for dyn loading in... |
[
{
"msg_contents": "What is the ideal setup to have when contributing to PG development? I can\nalways just download the latest CVS tree, and then presumably run diff when\nI want to send something in.\nHowever, my understanding is that using CVSup allows me to replicate the cvs\ntree into my own repository, wh... |
[
{
"msg_contents": "Forwarding this to the hackers list, since I can confirm the problem\nstill exists in 6.5.0. Looks like the functional extension of the\nearlier problem reported with default constant values being longer\nthan the field. Note trhat it is causing corruption, Leon's username \nwas just too shor... |
[
{
"msg_contents": ">Sorry, I think it is too late be adding port-specific feature to 6.5.1. \n>I will put it in 6.6. 6.5.1 release is due the 19th.\n\n\nWell, the current Makefile.shlib REL6_5_PATCH has been checked \nin today, and IS BROKEN for irix5, as I said.\nSo I would apply. The only difference it actua... |
[
{
"msg_contents": ">> Ok, sorry I see the difference now. Those that are for linking are named\n>> lib*.so\n>> and those that are for dyn loading into postgres don't have the lib.\n>\n>What? They should all have the \"lib\" AFAIK --- dynamic loading takes\n>the same kind of shared lib as a regular link does on... |
[
{
"msg_contents": "It took a little work to recompile after the include-file cleanups :-(.\nYou got overenthusiastic about removing #includes, apparently.\nI have checked in changes for the ones that caused compile failures\nor warnings here, but there may be more.\n\nOne thing that particularly disturbs me is ... |
[
{
"msg_contents": "Hi,\n\nA few weeks ago I sent an email out about getting BTP_CHAIN faults when\ntrying to perform operations with tables. My colleague Matt Altus was\ntrawling the mailing lists looking for information about this, and he\nfound some articles previously discussing problems with Btree indices a... |
[
{
"msg_contents": "I noticed that PostGress haven't any mechanism for\nsplit tables over a lot of device (Oracle-like).\n \nI wont write it. Can you authorize me?\n \nTIA\n---\nRoberto Colmegna\nRColmegna@YouOnLine.Org Roberto2312@hotmail.com\n\n\n\n\n\n\n\n\nI noticed that PostGress haven't any mechanism fors... |
[
{
"msg_contents": "Well, this is what I have discovered so far:\n\nI left BLCKSZ as it was, but adjusted MAX_QUERY_SIZE to 65535, and ran make.\nI tried to run a 50k query, and it worked; it took a while, but the results\nwere fine. So, as a temporary solution to this problem, you should be able\nto set MAX_QU... |
[
{
"msg_contents": "We've now got a viable mechanism for generating man pages from sgml\nsources. So, I'm starting to go through the old man pages (those in\nsrc/man/) to verify that all information in them is available\nsomewhere in the new docs.\n\n>From here on, there is no need to update the src/man/ man pag... |
[
{
"msg_contents": "Can I have votes on what people want the next version number to be?\n\nWe have to brand the release when we start development(PG_VERSION file).\n6.5 probably should have been called 7.0, but we had already committed\nto 6.5.\n\n\n-- \n Bruce Momjian | http://www.op.ne... |
[
{
"msg_contents": "I have marked the version as 6.6. Initdb everyone. You may also want\nto remove config.cache, as I have removed some old stuff.\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 ... |
[
{
"msg_contents": "I think I am going to get the award for most maligned piece of code that\nno one can figure out how to improve.\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 ... |
[
{
"msg_contents": "Per Leon's recent gripe in the bugs list, I have confirmed that\n\ncreate table t1 (f1 int4, f2 timestamp default text 'now');\n\ndoes *not* work as expected --- the stored constraint expression\nhas been pre-reduced to a timestamp constant, even though you\nget the desired behavior with\n\nc... |
[
{
"msg_contents": "BENCHMARK SUPPLY\n7540 BRIDGEGATE COURT\nATLANTA GA 30350\n\n***LASER PRINTER TONER CARTRIDGES***\n***FAX AND COPIER TONER***\n \n CHECK OUT OUR NEW CARTRIDGE PRICES :\n \n\nAPPLE \n \n LASER WRITER PRO 600 OR 16/600 $69\n LASER WRITER SELECT 300,310.360 $69\n LASER WRIT... |
[
{
"msg_contents": "Would someone who has the 6.5.1 release tree please update this file\nform me. It is docs/README.NT:\n\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 A... |
[
{
"msg_contents": "I don't see this feature in Oracle or Gray' book so I would\nlike to know what do you think about ability to have more than\n1 log to let different transactions write to different logs,\nin parallel. All log records from particular transaction will\ngo in one log file (one fsync on commit). T... |
[
{
"msg_contents": "I have gotten the right cvs tree, and updated it myself.\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": "Ditto.\n>> \n>> > Naming it 7.0 IMHO requires transaction log, tuple split over\n>> > blocks, foreign keys, outer joins and rules of arbitrary\n>> > size. I don't expect ALL of them for the next release, so let\n>> > it be 6.6.\n>> \n>> I like Jan's more complete list...\... |
[
{
"msg_contents": "Once a new tag or release has been applied to the CVS tree, is a new\ncheckout required, or can I just update with the new tag? Do I need to\nspecify a tag when updating? If not, which branch is used? Are there\nseparate branches for 6.5 bug-fixes and 6.6 development?\n\nMikeA\n\n",
"m... |
[
{
"msg_contents": "Good question. I was going to do a fresh checkout tomorrow, but it would\nbe interesting to know about this.\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-----\... |
[
{
"msg_contents": "Hi, \n\nI'm back from vacation.\n\nThere seems to be a typo in os.h. It says '#if if defined(__i386__)'. I\nthink there's one if too many. Could anyone please remove it. I do not have\nthe whole source checked out, so I cannot do it myself at the moment.\n\nMichael\n\n-- \nMichael Meskes ... |
[
{
"msg_contents": "This was exactly what I was looking for, thanks Tom.\n>> \n>> The tip of the tree (checkout with no branch or tag) is always the\n>> latest code; currently it is 6.6-to-be. For the last couple \n>> of versions\n>> we have made a practice of starting a branch for back-patch \n>> corrections\n... |
[
{
"msg_contents": "> Bruce.\n> \n> May be, you'll note this 6.5 revisions as the first _commerce quality \n> revisions_.\n> \n> I estimate 6.3 as the first _stable_ revision, and new 6.5 as the first \n> _high stable_ revision versions.\n\nYes. It seems 6.5 is much more stable, but it is hard for us to know\nt... |
[
{
"msg_contents": "> [I sent this to pgsql-docs, which bounced it as being over 40k. I'll leave\n> you to publicise it as you wish.]\n\nThe \"patches\" list is the only one without that restriction...\n\n> I attach a patch containing corrections to the Tutorial and User's Guide for\n> spelling, grammar, euphon... |
[
{
"msg_contents": "Thanks all for this info. I'm presuming that, because no-one has been rude\nyet, that a lot of this is not in the developers manual, or FAQ yet. Would\nit be worthwhile putting it there? Just a quick paragraph with the latest\nsettings, and default options for particular types of developer... |
[
{
"msg_contents": "Package: postgresql-contrib\nVersion: 6.5-2\n\nDear PostgreSQL hackers,\n\nI have sent this message to pgsql-general and so far received no reply. \nThis bug seems to be 100% reproducible on Linux (i386 and sparc). If this\nproblem is specific to Debian, then it would help me to know that, to... |
[
{
"msg_contents": "Hey hackers - \nI don't know if this is fixed in 6.5.1 or not, but the definition field\nin the pg_views system table is broken in 6.5.0, and this breaks view\nediting in pgaccess. The problem is that table qualifications are left\noff the fieldnames in both the SELECT clause and the WHERE cl... |
[
{
"msg_contents": "One last missing quoting bug in pg_dump:\nnow that sequence names are properly quoted for field defaults, mixed\ncase sequence names are generated. These are properly quoted in the\nCREATE SEQUENCE lines, but not in the SELECT nextval lines, as per below:\n\nCREATE SEQUENCE \"Teams_TeamID_seq... |
[
{
"msg_contents": "Herouth Maoz <herouth@oumail.openu.ac.il> writes:\n>> I think the problem results from using non-standard constructs such as\n>> order by expression, and indeed ordering by columns that don't appear in\n>> the select list.\n\nI replied:\n> No, that's not the problem.\n\nLooks like I spoke too... |
[
{
"msg_contents": "Thanks to our fine 6.5 release, the development history article, and my\nstatus report e-mail, in the past few days, I have heard:\n\n Jolly is very proud we have done so much with Postgres95.\n\n Someone wants me to speak to a Linux group meeting in New York City.\n\n Someone wants to tra... |
[
{
"msg_contents": "Hi all,\n\nI have a question about the calculation of selectivity.\n\nI see the following code in set_rest_selec() in clausesel.c.\n\n cost_clause = clausenode->selectivity;\n\n\t /*\n * Check to see if the selectivity of this clause or any\n'or'\n ... |
[
{
"msg_contents": "Try this one:\n\ncreate table fltsrc (f1 float8);\ninsert into fltsrc values (1.0);\ninsert into fltsrc values (1.1);\ncreate table intdest (f1 int4);\ninsert into intdest select distinct f1 from fltsrc;\n\nCurrently, this coredumps because it tries to apply float8lt\nto integer values; the r... |
[
{
"msg_contents": "In merging the man pages, I find that CREATE VERSION is marked as not\nworking in the current release. Did we lose that capability when we\nlost time travel, or is that something separate? If it is not related\nto time travel, why doesn't it work currently?\n\nIf this is to complicated to ans... |
[
{
"msg_contents": "Me, again...\n\nIn psql, is the \\ that appears before a command supposed to terminate the\nexisting query line (if any), as well as escape the command from the query?\nIt seems that way, because anything after a \\ command is ignored totally,\neven another command. Once the command has been... |
[
{
"msg_contents": "\nBefore I announce this, can someone confirm that its okay as bundled? I\nbelieve I've covered everything, but figure that a second opinion is\nalways nice :)\n\nMarc G. Fournier ICQ#7615664 IRC Nick: Scrappy\nSystems Administrator @ hub.org \nprimary: scrapp... |
[
{
"msg_contents": "Tom Lane wrote:\n>> buffer indefinitely extensible, I'd counsel fixing one bug \n>> at a time...\nI know, you're right.\nI'm not trying to fix it, though, only trying to work out what it is\nsupposed to do in certain circumstances.\n\n\nMikeA\n",
"msg_date": "Tue, 20 Jul 1999 17:30:04 +02... |
[
{
"msg_contents": "In order not to break it. I could just run the regression tests, I suppose,\nbut it always helps if you kind of know where you're going.\n\n>> -----Original Message-----\n>> From: Ansley, Michael [mailto:Michael.Ansley@intec.co.za]\n>> Sent: Tuesday, July 20, 1999 5:30 PM\n>> To: 'pgsql-hack... |
[
{
"msg_contents": "Please Cc: to teo@flex.ro\n\nHello all,\n\nI think I have found a bug in unique index.\nThe bug has been tested with:\n-PostgreSQL 6.5 final version running on a RedHat 5.2 i386\n-PostgreSQL 6.5 final version running on a RedHat 6.0 i386\n-PostgreSQL 6.4.2 running on a RedHat 5.2 i386\nand th... |
[
{
"msg_contents": "> > I imagine that this flag is specific to the compiler. It would\n> > probably be best to leave it to patches until the alpha issues are\n> > solved for every OS environment; sorry I don't have a platform myself\n> > to test on.\n> > \n> > btw, RedHat is interested in doing a maintenance re... |
[
{
"msg_contents": "Looks like I am going to be in the cache for some time, adding indexes\nto system tables that are difficult to do.\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, | 8... |
[
{
"msg_contents": "\nIts now been a month since the release of v6.5, and the PostgreSQL Global\nDevelopment Group is pleased to announce the release of v6.5.1, which is\nfocused on addressing any bugs or issues post-release:\n\n Fix for datetime constant problem on some platforms(Thomas)\n Add NT RE... |
[
{
"msg_contents": "> Hello,\n> \n> Just my IMHO you should not break your tree for commercial and non\n> commercial, you can make more than enough money just from offering\n> commercial support for the database. \n> \n> If you want to get sickly rich make sure NOBODY can sell it and that they\n> can only provid... |
[
{
"msg_contents": "Hi,\n\nWell, I got psql to do it's thing, eventually. I've tested it for pretty\nmuch everything, including \\e, \\g, \\r, \\i. \nThe one problem that I have had is that after about the third '\\i long.sql',\nI get a core dump, because sprintf moaned about string size complications.\nThe wa... |
[
{
"msg_contents": "Hello!\n\n I've sent 3 mails to pgsql-patches. There are two files, one for doc and\nfor src/data directories, and one minor patch for doc/README.locale.\n Please apply.\n\nOleg.\n---- \n Oleg Broytmann http://members.xoom.com/phd2/ phd2@earthling.net\n Programmers do... |
[
{
"msg_contents": "> Hi, Massimo,\n> \n> You might have noticed my posting a couple of days back about the max query\n> string length problem. I was referred to you by Tom Lane, as he says that\n> you've done some work in this area. I'd like to sort this out, mainly\n> because I'd like to get involved in the ... |
[
{
"msg_contents": "\nI've been reading up on what Informix and Oracle provide in the way of\nobject support.\n\nIn particular I noticed that in Informix when you SELECT on a table it\nby default includes all the objects of sub-classes. In other words the\n\"*\" is postgres terms is always there by default. If y... |
[
{
"msg_contents": "\nIn implementing a core Text C++ class object, \nwe use realloc() without problems. However, with\nregard to resizing, we always DOUBLE the existing\nsize of the buffer when the string needs to be \nexpanded so that it doesn't take 100 iterations\n(and therefore 100 realloc()'s) to create a... |
[
{
"msg_contents": "If there was enuff interest (I'm not siding one way or the other) you could\nadd in a global setting to change the default.\nI was also curious as to why these msgs are cross posted in 3 different\ngroups...\n-----Original Message-----\nFrom: Tom Lane <tgl@sss.pgh.pa.us>\nTo: Chris Bitmead <c... |
[
{
"msg_contents": "\nJust a quick note to say that my home email is now working again,\nalthough I've yet to get procmail working again, so everything is in my\ninbox (ouch).\n\nAnyhow, because I ended up reinstalling my server (installed an ISDN card,\nand couldn't get RedHat to recognise it - I'm now running ... |
[
{
"msg_contents": "Don't kill a psql client that's in the middle of a COPY IN operation.\n\nWith current sources, the connected backend fails to quit, but instead\ngoes into an infinite loop writing\npq_recvbuf: unexpected EOF on client connection\nto stderr over and over.\n\nIf you have postmaster stderr direc... |
[
{
"msg_contents": "Hi all,\n\nA question about TODO item\n * Fix memory exhaustion when using many OR's\n\npull_ors() and pull_ands() are called while processing \ncnfify() and both call copyObject().\n\t\t ^^^^^^^^^^^^^^\nFor example in pull_ors()\n\n\treturn (pull_ors(nconc(copyObject((Node *) args),\... |
[
{
"msg_contents": "Hi,\n\nI am trying to write an interface for accessing the postmaster and\nsubsequently a postgres database server in a language that our group has\nwritten, which is called APRIL. However, I am having a few problems\nmaking the connection.\n\nI appear to be able to make a successfuly connect... |
[
{
"msg_contents": "subscribe\n\n",
"msg_date": "Thu, 22 Jul 1999 09:22:04 +0200",
"msg_from": "\"F.J.Cuberos\" <fjcuberos@infomail.lacaixa.es>",
"msg_from_op": true,
"msg_subject": ""
}
] |
[
{
"msg_contents": "Hello!\n\n Oliver pointed that my English was not good enough and suggested ways to\nimprove my docs. Below is a minor patch for doc/README.locale (the patch\nshould be applied after the patch I've sent yesterday).\n\n*** README.locale.orig\tWed Jul 21 13:42:28 1999\n--- README.locale\tThu ... |
[
{
"msg_contents": "Massimo wrote:\n>> A better way would be to allocate and grow query buffers dynamically\nwhile\n>> reading the query but you will anyway have troubles with lex and yacc\nwhich\n>> use statically allocated buffers whose size is hardwired in the program.\n>> This is why I had to make those ugly... |
[
{
"msg_contents": "\nHi,\n\nI need set lock table privilage for user, but now I must grant upload\npriv. for it. But I needn't upload priv. for user. Upload is possible\nvia RULEs without GRANTed (upload) privilage for user.\n\nMy suggestion is add to GRANT command LOCK privilage.\n\n ....\n privilege is {ALL ... |
[
{
"msg_contents": "Using 6.5 (via Thomas Lockhart's Linux RPM build of Jul 2), I get a\nphantom row when doing the following:\n\n create table foo (a int);\n select t1.a, count(*) from foo t1, foo t2 group by t1.a;\n\nI get\n\n a|count\n -+-----\n | 0\n (1 row)\n\ninstead of zero rows. The... |
[
{
"msg_contents": "subscribe\n\n",
"msg_date": "Thu, 22 Jul 1999 17:59:06 +0200",
"msg_from": "\"F.J.Cuberos\" <fjcuberos@infomail.lacaixa.es>",
"msg_from_op": true,
"msg_subject": ""
}
] |
[
{
"msg_contents": "I just tried to run initdb with the latest CVS snapshot but initdb\nsegfaults, i.e. some programs inside do:\n\nVacuuming template1\nSegmentation fault\nSegmentation fault\nCreating public pg_user view\nSegmentation fault\nSegmentation fault\nSegmentation fault\nCreating view pg_rules\nSegmen... |
[
{
"msg_contents": "\nMorning all...\n\n\tJust had someone inquire as to whether any of the 'Fortune 500'\ncompanies are using PostgreSQL ...\n\n\tDon't know the answer myself...anyone out there associated with\none willing to speak out?\n\n\t\n\nMarc G. Fournier ICQ#7615664 IRC N... |
[
{
"msg_contents": "\n*** dynloader.c.old\tThu Jul 22 16:29:46 1999\n--- dynloader.c\tThu Jul 22 16:30:23 1999\n***************\n*** 1,6 ****\n /* Dummy file used for nothing at this point\n *\n- <<<<<<< linux.c\n * see sunos4.h\n =======\n * dynloader.c\n--- 1,5 ----\n***************\n*** 16,25 ****\n ... |
[
{
"msg_contents": "Hello PostgreSQL hackers - \nI'm considering trying to implement a new feature that would have some\ninteresting possible uses. I'm wondering how difficult it would be\nto implement a table who's content does not come out of the files on\ndisk, but instead is accessed remotely from another d... |
[
{
"msg_contents": "\n> > select t1.a, count(*) from foo t1, foo t2 group by t1.a;\n> \n> Still, I must say that a row returning \"0\" in response to a \n> count(*) isn't at all suprising, I guess it's a matter of \n> whether or not the count(*) or the specific column being\n> extracted determines the behavi... |
[
{
"msg_contents": "subscribe fjcuberos@infomail.lacaixa.es\n\n",
"msg_date": "Fri, 23 Jul 1999 11:11:54 +0200",
"msg_from": "\"F.J.Cuberos\" <fjcuberos@infomail.lacaixa.es>",
"msg_from_op": true,
"msg_subject": ""
}
] |
[
{
"msg_contents": "Currently, in postgreSQL, primary keys are created as a UNIQUE index on the\nfield(s) that form the primary key.\n\nThis means that there is no difference between explicitely declaring a\nPRIMARY KEY in your table definition or using the CREATE UNIQUE INDEX\ncommand.\nThere is one caveat to t... |
[
{
"msg_contents": "A very useful feature in some database systems is the ability to restrict who can run certain external or stored procedures, and to grant extra access rights to users when they do run those procedures.\n\nThe usefulness of this may not be imediately obvious, but it is a very powerful feature,... |
[
{
"msg_contents": "(Note to hackers: Ole sent me a 1000-row test case off list.)\n\n> oletest=> explain select * from av_parts where partnumber = '123456';\n> NOTICE: QUERY PLAN:\n> \n> Index Scan using av_parts_partnumber_index on av_parts (cost=2.04 rows=1\n> width=124)\n> \n> EXPLAIN\n> oletest=> explain s... |
[
{
"msg_contents": "I've been reading Ole's posts with great interest\nas we've have just experienced similar problems\nourselves here. I opened up a Slip ;-) #5 but \nI've narrowed down the difference between two \nqueries which illustrate the problem:\n\nThe first query:\n\nSELECT DISTINCT \nsupplies.supply,s... |
[
{
"msg_contents": "Magnus Hagander <mha@sollentuna.net> writes:\n> I've now finished \"polishing off\" my old SSL code, and rewritten it to work\n> with 6.6 (current snapshot). Included is the patch against the cvs tree from\n> Jul 22nd.\n\nCool. Secure connections are good.\n\n> Unfortunatly, in order to allo... |
[
{
"msg_contents": "> > Unfortunatly, in order to allow for negotiated SSL, this \n> patch breaks the\n> > current protocol (meaning old clients will not work with \n> the new server, and\n> > the other way around). I felt it was better to break this \n> here, than to\n> > break the frontend API (which would oth... |
[
{
"msg_contents": "\nToday I got familiar problem with vacuum analyze\n\ndiscovery=> select version();\nversion\n------------------------------------------------------------------------\nPostgreSQL 6.5.1 on i686-pc-linux-gnulibc1, compiled by gcc egcs-2.91.66\n(1 row)\n\ndiscovery=> vacuum analyze;\nNOTICE: Ab... |
[
{
"msg_contents": "on the patches list, I posted the first files\nfor suuport for using perl as the procedural\nlanguage.\n\nThe makefile uses libtool (probably incorrectly).\n\nIt is not 'safe'.\n\nPerl XS modules cannot be used.\n\nUsing Perl in rules hasn't even been thought about.\n\nIF the code looks suspi... |
[
{
"msg_contents": "Hi everyone!\n\nYou may remember me as the one who was having lots of trouble using\nPostgres 6.4.2 with spinlock, BTP_CHAIN, and other miscellaneous problems.\nI tried patches and other tricks but everything was running really badly\nand we constantly had to intervene to keep the database ru... |
[
{
"msg_contents": "Hi,\n\nI sent a bug report in a week ago about problems with pg_proc and getting\nSIGSEGV when trying to create largish functions.\n\n[please see my previous posting for details]\nI'm not sure what to do here, I tried dropping the pg_proc_prosrc_index\nand it died, and so I have to leave it h... |
[
{
"msg_contents": "Hello, Could you please help me with my problem. I am currenlty implementing somewhat of a proxy. Meaning, there will be a lot of sql queries doing at the same time. Every URL address will be check whether it exist in the database. After opening a lot of sites, suddenly i receive a \"backend ... |
[
{
"msg_contents": "I did some benchmarks of my Web site and notice I lost some hits\nwhich I accumulate in postgres (6.5.1) database on Linux 2.0.36 system\n\nHere is what I had before testing - 181 hits for msg_id=1463\n\n 1463| 181|Sat 24 Jul 12:12:24 1999 MSD|Sat 24 Jul 12:12:34 1999 MSD\n(11 rows)\n\n12:1... |
[
{
"msg_contents": "I answer to my previous post:\n\nProbably ab reports wrong number of requests and \nrecords from access_log and hits from database are consistent,\n\nSo, probably there are no problem with database,\nbut I'd like to know do I need something else to safely log\ninto database.\n\n\tRegards,\n\n... |
[
{
"msg_contents": "At 08:54 23/07/99 -0300, The Hermit Hacker wrote:\n>\n>Can't we do this already with views?\n>\n\nNot really. A combination of Views, Triggers and Rules will almost do it,\nbut at the expense of being harder to maintain and more difficult to\nunderstand. It may be worth giving a real-world ex... |
[
{
"msg_contents": "At 10:51 23/07/99 -0400, you wrote:\n>\n>We have some of this, I think, from ACLs on tables and views. But\n>as far as I know there is not a notion of a \"suid view\", one with\n>different privileges from its caller. It sounds like a good thing\n>to work on. Is there any standard in the ar... |
[
{
"msg_contents": "subscribe\n\n\n",
"msg_date": "Sat, 24 Jul 1999 15:43:16 +0200",
"msg_from": "\"F J Cuberos\" <fjcuberos@infomail.lacaixa.es>",
"msg_from_op": true,
"msg_subject": ""
}
] |
[
{
"msg_contents": "Will there be a 6.5.2 release? Due to me being late a the latest bug fixes\nin ECPG didn't make it into 6.5.1. They are in the archive at the moment\nthough.\n\nMichael\n-- \nMichael Meskes | Go SF 49ers!\nTh.-Heuss-Str. 61, D-41812 Erkelenz | Go Rhein Fire!\nTel.: ... |
[
{
"msg_contents": "On Saturday, July 24, 1999 5:37 PM, Tom Lane [SMTP:tgl@sss.pgh.pa.us] wrote:\n> I wrote:\n> > [ a bunch of stuff ]\n> \n> After looking into this morning's patches digest, I see that half of\n> this already occurred to you :-).\n> \n> I'd still suggest extending the client to fall back to non... |
[
{
"msg_contents": "Hello,\n\nSorry for long postings. I'm triyng to identify my problem with logging \nto Postgres.\n\nI have some problem with comparison of accumulated hits count\nfrom DB, from apache's access_log and what test tool reports (I'm using\nab which comes with apache distribution). \nIt's obvious ... |
[
{
"msg_contents": "> > As it is right now, it should work in all combinations except a 6.6\nclient\n> > compiled with SSL support connecting to a pre-6.6 server. It already\n> > falls-back if the server is 6.6 (without SSL support). And the 6.6\nclient\n> > compiled without SSL works.\n> \n> Actually, it should... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.