Dear all of you,
I'm currently working on a centos that I manage with webmin.
A sI try to create a DB with unicode encoding the following message is
returned to me :
new encoding (UTF8) is incompatible with the encoding of the
template database (SQL_ASCII)
After a little googling,
> On Wed, Jan 14, 2009 at 07:36:03PM -0800, mailingli...@net-virtual.com
> wrote:
>> CREATE TABLE listings (
>> trans_id SERIAL,
>> mode CHAR(1),
>> listing_id INT,
>> region_id INT,
>> category INT
>> );
>>
>> "SELECT * FROM listings ORDER BY region_id, category, listing_id,
>> trans_id
Hello,
Thanks to the replier (Martijn -- thank you very much!) to an earlier
question I had about MVCC, I've decided to re-think entirely my use of the
status column in a table. What I've decided to do is to put all of my
new or changed records into a "holding" table, then after they are
indexed
Hello,
I have a couple of questions regarding how MVCC (in postges 8.3.3 if it
makes a difference) affects vacuum.
#1. If I am doing an update to a row and none of the values have changed,
will that cause a "hole" that requires vacuum to reclaim?
#2. I have a column in my table (called "status",
> Phil Endecott <[EMAIL PROTECTED]> writes:
>> I would understand this if I were doing an "ALTER TABLE", for example.
>> But does adding or removing a trigger really count as "schema-altering"?
>
> [ shrug... ] Hard to say. Probably depends a lot on what the trigger
> does. I suppose we could
