[GENERAL] files stored in the database

as it keeps coming up on the list off and on, I decided to write a wiki article, comments suggestions http://wiki.postgresql.org/wiki/BinaryFilesInDB I also read over the 9.0 beta release notes, bytea type now allows hex values??

Re: [GENERAL] PG random() strangeness

Message from mailto:m...@sai.msu.ru Sergey E. Koposov m...@sai.msu.ru at 05-04-2010 06:36:23 PM -- Hello, I'm getting strange results with PostgreSQL random() function. It would be great if someone could either show where I am wrong or PG is wrong. Here is what I do (PG 8.4.3,

Re: Fwd: [GENERAL] Tablespace Problem

Message from mailto:softlinne...@gmail.com Kalai R softlinne...@gmail.com at 05-03-2010 05:41:24 PM -- Hi, Sir, I have been checked pg_tblspc/86014 directory have no permission to create new folder. I am using Windows XP Os and VB.Net frontend. I created the tablespace folder by

Re: [GENERAL] PostgreSQL vs. Microsoft SQL server

On Sat, 2010-05-01 at 20:47 +0200, Thomas Løcke wrote: --Anybody know of any recent comparisons made between the two? I'm in the process of buying a new telephony related software suite, and I'm getting mixed advice. Some say that MSSQL is _much_ better/faster than PostgreSQL, and others say

Re: [GENERAL] Am I supposed to be all scared of compound primary keys?

On Sat, 2010-05-01 at 19:25 -0700, Mike Christensen wrote: --I have a table that stores a user ID and a subscription type, and this is really all it needs to store and any pair of values will always be unique. In fact, I think this pair should be the primary key on the table. However, I'm

Re: [GENERAL] ERROR: cache lookup failed for relation X

Because You dropped/deleted the table cache in Session A. The simplest way to look at it is Session B was lock out when the Drop table command was issued from Session A. Now when session B finally got its chance to drop/delete the table it was already gone . What kind error were you expecting

Re: [GENERAL] MS Access 2007 update write conflict problem resolution

The bigger problem is using time stamps to find the record for updating Timestamps will not be unique as more than 1 record can have the same value I suggest changing the updating method to use a unique key. Message from mailto:douglas.lit...@orbitz.com Little, Douglas

Re: [GENERAL] MS Access 2007 update write conflict problem resolution

. Message from mailto:richard.broer...@gmail.com Richard Broersma richard.broer...@gmail.com at 03-19-2010 01:12:35 PM -- On Fri, Mar 19, 2010 at 11:12 AM, jus...@magwerks.com jus...@magwerks.com wrote: The bigger problem is using time stamps to find the record for updating Timestamps