Hi all,
I'm trying to find less than and greater than functions for
datetime types. It doesn't look the the time interval operators
would be appropriate, but I haven't found anything else in the
docs. Here's my snippet of plpgsql which fails:
select count(*) into rescount
from current
> On Thu, Jan 20, 2000 at 05:18:36PM -0500, Bruce Momjian wrote:
> > > The standard doesn't provide for specifically unsigned types, so I do not
> > > believe anyone would want to go through that trouble. Sorry.
> >
> > Actually, oid data type is an unsigned int4. If it does not behave that
> >
On Thu, Jan 20, 2000 at 05:18:36PM -0500, Bruce Momjian wrote:
> > The standard doesn't provide for specifically unsigned types, so I do not
> > believe anyone would want to go through that trouble. Sorry.
>
> Actually, oid data type is an unsigned int4. If it does not behave that
> way, it is a
[Charset ISO-8859-1 unsupported, filtering to ASCII...]
> The standard doesn't provide for specifically unsigned types, so I do not
> believe anyone would want to go through that trouble. Sorry.
Actually, oid data type is an unsigned int4. If it does not behave that
way, it is a bug.
--
Bruc
The standard doesn't provide for specifically unsigned types, so I do not
believe anyone would want to go through that trouble. Sorry.
On 2000-01-19, Martin Neumann mentioned:
> Are there any plans to implement unsigned datatypes like uint4 and
> uint8?
>
> In many cases I don't need the signed
> I have been looking at the psql documentation posted on the web
> site. I am trying to set variables, but I can't seem to make that
> happen. I also notice that psql doesn't seem to parse full
> backslash commands. Are the documents out of date, or is the a bug?
>
> \echo foo
>
> is interp
I can understand that. What's weird is that I can do a sum(amount) on
the whole table and the value comes out to only My only problem is that
the amount field is the money type and doesn't like the casting now. A
SELECT SUM(amount::float8) FROM table where state = 'CA';
returns
Hi,
I have troubles inserting the timestamp values. I use postgresql 6.5.3
on RedHat 6.1 (kernel 2.2.13). I do the following
sample==> create table t1 (d timestamp);
CREATE
sample==> create index t1_d on t1 using btree (d datetime_ops);
CREATE
sample==> insert into t1 (d) values ('1999-01-01 14:
I have been looking at the psql documentation posted on the web
site. I am trying to set variables, but I can't seem to make that
happen. I also notice that psql doesn't seem to parse full
backslash commands. Are the documents out of date, or is the a bug?
\echo foo
is interpreted as \e and
Dan Reish wrote:
>
> Does anyone know where I might find documentation on creating R-tree indexes
> in PostgreSQL? The docs included in the standard distribution don't seem to
> even mention the existence of R-trees.
There is some brief mention as to bugs in R-Trees in some part of the
document
I had this problem a couple years ago. I changed the column name
before the upgrade by renaming the table to table_old, creating a
new table with the original table name by selecting from table_old.
For the column I needed to rename, I selected offset as
'x_offset'. I made sure everything was
> Am I the only one who cannot vacuum a named table? (Does it make sense to
> just vacuum a single table?)
>
> regression=> \h vacuum
> Command: VACUUM
> Description: Clean and analyze a Postgres database
> Syntax:
> VACUUM [ VERBOSE ] [ ANALYZE ] [ table ]
> VACUUM [ VERBOSE ] ANALYZE [ table [
Does anyone know where I might find documentation on creating R-tree indexes
in PostgreSQL? The docs included in the standard distribution don't seem to
even mention the existence of R-trees.
Thanks.
--
Dan
List of databases
Database | Owner
+--
Newnham| prlw1
% psql Newnham
psql: connection to database "newnham" failed - FATAL 1: Database "newnham" does not
exist in the system catalog.
template1=> \c 'Newnham'
FATAL 1: Database "newnham" does not exist in the
Yury Don wrote:
Hello All,
I ma sorry, I have sent previous uncomplited e-mail accidentally.
I have created the table
CREATE TABLE "tt" (
"cc" int4);
COPY "tt" FROM stdin;
-2112563299
-2111287024
-2110307960
.
2146589610
2146589611
2146589612
\.
About 30 000 records totally
Then I a
Am I the only one who cannot vacuum a named table? (Does it make sense to
just vacuum a single table?)
regression=> \h vacuum
Command: VACUUM
Description: Clean and analyze a Postgres database
Syntax:
VACUUM [ VERBOSE ] [ ANALYZE ] [ table ]
VACUUM [ VERBOSE ] ANALYZE [ table [ (column [, ...] )
Hello Richard,
Once, Thursday, January 20, 2000, 3:04:43 PM, you wrote:
RH> - Original Message -
RH> From: Yury Don <[EMAIL PROTECTED]>
RH> To: pgsql-general <[EMAIL PROTECTED]>
RH> Sent: Wednesday, January 19, 2000 11:32 AM
RH> Subject: Re[2]: [GENERAL] Bug or my crooked hands?
>> >> I
Is it possible to create an alias for an existing type, so that I can refer to
it with a simple name, and possibly change it in the future? Something like:
create type-alias issn as char(9)
Without that it looks like I have to do
create type issn (
input=charin, output=charout,
inte
On Thu, 20 Jan 2000, Marc Tardif wrote:
> In the contrib directory, there is an example on how to redirect apache
> logs to a postgresql database. It says to create a table and change two
> lines in the apache configuration file to use psql for copying the
> logs to the database.
>
> My question
- Original Message -
From: Yury Don <[EMAIL PROTECTED]>
To: pgsql-general <[EMAIL PROTECTED]>
Sent: Wednesday, January 19, 2000 11:32 AM
Subject: Re[2]: [GENERAL] Bug or my crooked hands?
> >> I have the following situation:
> >>
> >> CREATE TABLE "Contacts" (
> >> "Contact"
test_table has to be created by different user than testuser. If the table
is created by testuser he is an owner of the table and can do everything
what he wants.
Regards,
Andrzej
> -Original Message-
> From: Balazs Gyetvai [SMTP:[EMAIL PROTECTED]]
> Sent: 20 stycznia 2000 11:07
> To: [
I'm having a problem, both through JDBC and through psql (so I reckon
the problem is in the core database) whereby if I put a value into a
timestamp field which has a non-unique index on it, I get a "back-end
has died unexpectedly" error.
It's consistently happening on the same column in the same
> Hello
>
> I like to create a user who can do the followings on a table: select,
> insert, update
> But he can't delete!
> I tried this: grant INSERT, SELECT, UPDATE on table_name to testuser;
> After this the test user can delete from the table_name table without any
> problems. The testuser is
Hello
I like to create a user who can do the followings on a table: select,
insert, update
But he can't delete!
I tried this: grant INSERT, SELECT, UPDATE on table_name to testuser;
After this the test user can delete from the table_name table without any
problems. The testuser is not a superuse
Hello All,
I ma sorry, I have sent previous uncomplited e-mail accidentally.
I have created the table
CREATE TABLE "tt" (
"cc" int4);
COPY "tt" FROM stdin;
-2112563299
-2111287024
-2110307960
.
2146589610
2146589611
2146589612
\.
About 30 000 records totally
Then I am doing the fo
25 matches
Mail list logo
