Tom Lane writes:
> [EMAIL PROTECTED] writes:
> > This is with regards to Postgres 6.5.
> > While trying to ALTER RENAME a large table (203MB data file), an error
> > occured.
>
> Table RENAME is pretty risky under 6.5 :-(. 7.0 is a little better,
> but RENAME will never be trustworthy until we
Ross J. Reedstrom writes:
> On Wed, Aug 16, 2000 at 02:36:10PM +, [EMAIL PROTECTED] wrote:
> >
> > This is with regards to Postgres 6.5.
> >
> > While trying to ALTER RENAME a large table (203MB data file), an error
> > occured. \d displays the new table name, but there is no correspondin
Don Baccus writes:
> At 01:06 PM 8/1/00 +1000, Philip Warner wrote:
>
> >I agree; it's definitely a non-critical feature. But then, it is only 80
> >lines of code in one place (including 28 non-code lines). I am not totally
> >happy with the results it produces, so I have no objection to removi
[EMAIL PROTECTED] writes:
>
> I want to copy in some data from a tab-delimited flat file, but one of the
> columns that should translate into a datetime is in Unix timestamp format
> (seconds since epoch).
>
> The data should go into this table:
> create table logins (
> uname varchar(100
I want to copy in some data from a tab-delimited flat file, but one of the
columns that should translate into a datetime is in Unix timestamp format
(seconds since epoch).
The data should go into this table:
create table logins (
uname varchar(100),
timein datetime,
duration int,
Lincoln Yeoh writes:
> At 10:01 PM 26-06-2000 -0400, Michael Mayo wrote:
> >- Original Message -
> >From: "Lincoln Yeoh" <[EMAIL PROTECTED]>
> >> What are the recommended ways to do transactions in web applications?
> Let me illustrate the problem with an example:
>
> page 1
> user logs
The backend died while I was dropping an index on a table. Now I cannot
access my data! Help!
My table looks like
create table user_usage (email varchar(100),date date);
I created the index:
CREATE INDEX user_usage_email_idx on user_usage(email);
When I dropped the index, the backend died. No
