Hi there,
i'm planning to use the following trigger function to update a timestamp of
a row when it is UPDATEd:
CREATE OR REPLACE modified_trigger() RETURNS opaque AS $$
BEGIN
NEW.modify_timestamp := now();
END;
$$ LANGUAGE SQL;
Since i like to use the same trigger procedure for vari
// FIXED //
Tom, thank you so much for your help! Now running 8.1.2, the query now works
quickly and properly.
-Ben
On Wednesday 25 January 2006 13:17, Benjamin Smith wrote:
> Version: postgresql-8.1.0-4.c4
>
> I'll have to see about getting an update...
>
> Thanks a TON,
>
> -Ben
>
>
Anyone?
Op vrijdag 20 januari 2006 07:56, schreef Dick Kniep:
> Hi list,
>
> We are using logging in a database based on triggers and plpgsql functions.
> This works OK. However, we want deletes to be recorded too, and there we
> want the user who connected to be recorded in the log. So, how can I
Alex Mayrhofer wrote:
Hi there,
i'm planning to use the following trigger function to update a timestamp
of a row when it is UPDATEd:
CREATE OR REPLACE modified_trigger() RETURNS opaque AS $$
BEGIN
NEW.modify_timestamp := now();
END;
$$ LANGUAGE SQL;
I don't think you can write a t
surabhi.ahuja wrote:
Hi,
I am going to integrate my dtabase into a system. That system also
has another database and uses postgres.
However they have their own data directory and start postmaster by
specifying that.
I have seen that it is possible to run multiple postmasters on
multiple ports
Dick Kniep wrote:
Anyone?
I thought I saw an answer to this yesterday. Have you tried CURRENT_USER
? It's in the "functions and operators" section of the manuals (contrary
to appearance, it is a function).
Op vrijdag 20 januari 2006 07:56, schreef Dick Kniep:
Hi list,
We are using loggin
Robert Korteweg writes:
I have a problem with a database i'm maintaining. I first noticed
the problem because i could not make a backup of the database i got
the following error:
pg_dump: missing pg_database entry for database "xxx"
I verified this by selecting the pg_database. It was inde
andrew wrote:
I want to use a UDF to filter tuples t that are generated after a join.
More specifially, I have a UDF foo(record), which computes a value for
a given tuple. I can do the filtering before the join. e.g.:
select * from A, B where foo(A)<2 and A.a=B.b;
I suppose you mean where foo
Thanks, Tom. It is done by modifying coerce_type() and
can_coerce_type(). The reason I have to keep to verson 7.3 is I am
working on a research prototype that is built over pgsql 7.3. I need
the extra functions provided by that prototype.
On 1/25/06, Tom Lane <[EMAIL PROTECTED]> wrote:
> andrew <
Hi!
I have table with row named rank and some other rows. I have about
900.000 rows in table and I need to update
all rows with the same value of rank, so I run update table set rank = 1;
The only problem is speed. I'm waiting about 30 minutes and it's still
running.
My system is pg8.1 with
Uroš Gruber wrote:
Hi!
I have table with row named rank and some other rows. I have about
900.000 rows in table and I need to update
all rows with the same value of rank, so I run update table set rank = 1;
The only problem is speed. I'm waiting about 30 minutes and it's still
running.
My
Oops, Sorry, didn't get the answers untill just now...
Op donderdag 26 januari 2006 10:02, schreef Richard Huxton:
> Dick Kniep wrote:
> > Anyone?
>
> I thought I saw an answer to this yesterday. Have you tried CURRENT_USER
> ? It's in the "functions and operators" section of the manuals (contrary
Michael Crozier wrote:
I think I see now, "dead" tuples are the tuples that have yet to be
reclaimed
by vacuum, not tuples that are ready to be used. I'm still rather
confused,
as this table is only modified via inserts. No deletes or update
operations
are ever performed. Logically (ie "I do
that answered my question.
Thanks everyone
Patrick Hatcher
Development Manager Analytics/MIO
Macys.com
Michael Fuhr
<[EMAIL PROTECTED]>
Hi,
Is there a possibility to use "polish, Poland" locale from windows
version under linux? Locales = ISO8859-2 (pl_PL) has no collate order
for signs like space, dot,... ?
Filip
---(end of broadcast)---
TIP 4: Have you searched our list archive
Hi there,
i'm using the following trigger function to update a timestamp of a row when
it is UPDATEd:
CREATE OR REPLACE modified_trigger() RETURNS opaque AS $$
BEGIN
NEW.modify_timestamp := now();
END;
$$ LANGUAGE SQL;
Since i like to use the same trigger for various tables, i'm plan
In article <[EMAIL PROTECTED]>,
James Croft <[EMAIL PROTECTED]> wrote:
[given a bunch of temporary tables called session_data]
% How can I determine if one of the above relations is a temporary
% table in the current session (one of them, the first in ns 2200, is a
% normal permanent table)?
On Thu, Jan 26, 2006 at 10:13:52AM -0500, John D. Burger wrote:
> I suspect that if a transaction rolls back, any inserts done in the
> interim turn into dead tuples.
Yep:
test=> CREATE TABLE foo (x integer);
CREATE TABLE
test=> BEGIN; INSERT INTO foo SELECT 1 FROM generate_series(1, 1); ROL
Last week I upgraded from -7.4.3 to -8.1.2. I had some problems moving data
because of both my ignorance of the proper syntax and the move from
/usr/local/pgsql to /var/lib/pgsql. Now I cannot access the server:
[EMAIL PROTECTED] ~]$ psql -l
psql: could not connect to server: Permission denied
On 1/26/06 11:53 AM, "Rich Shepard" <[EMAIL PROTECTED]> wrote:
>Last week I upgraded from -7.4.3 to -8.1.2. I had some problems moving data
> because of both my ignorance of the proper syntax and the move from
> /usr/local/pgsql to /var/lib/pgsql. Now I cannot access the server:
>
> [EMAIL
On Thu, 26 Jan 2006, Rich Shepard wrote:
psql: could not connect to server: Permission denied
What do I do to trace the source of this problem and fix it?
Some progress to report. A Google search found a reply from Tom Lane last
month to someone reporting the same error. I changed permis
hi all,I am using PostgreSQL 8.0.1 on Fedora core 2.My goal is to create a common Exception handling stored function that takes Error Constant (as defined in Error Codes document: AppendixA) and raises a customized exception.
The problem is:(a) How do i catch these Error Constants? I was unable to
On Thu, 26 Jan 2006, Sean Davis wrote:
You did start the server? Did you fix the pg_hba.conf file? Does your
postgresql.conf file allow tcp connections? Those are the places I would
look.
Sean,
Thank you.
Yes, the server is running:
21839 ?S 0:00 /usr/bin/postmaster -D /v
Rich Shepard <[EMAIL PROTECTED]> writes:
> Now, I don't know that the server is accepting connections, but
> srwxr-xr-x 1 root root 0 2006-01-21 14:53 /tmp/.s.PGSQL.5432=
> exists as a socket.
>What do I do to trace the source of this problem and fix it?
That's got the wrong ownership (shoul
Rich Shepard <[EMAIL PROTECTED]> writes:
>So, now I can see the tables in the various databases, but SQL-Ledger still
> cannot:
>
> Internal Server Error
> The server encountered an internal error or misconfiguration and was unable
> to complete your request.
>
>How do I get this fixed, pl
Hey.
I am new here. I’m from Poland:-)
I have one question (I don’t now if this is the right group for this question
and … if my English is enough good… :P):
Are the developers going to implement some system trigger like in ORACLE i.e.
“on login” trigger ??
--
Best regards
LaroG
On Thu, 26 Jan 2006, Doug McNaught wrote:
That's a webserver error usually meaning a CGI script crashed or gave bad
output. Look in the webserver error log file to see what happened.
Doug,
Sigh. All I see there are references to SQL-Ledger scripts not finding
libraries (which are installed
I am looking into using WAL archiving for incremental backups. It
all seems fairly straightforward except for one thing.
So you set up the archiving of the WAL files. Then you set up cron
or something to regularly do a physical backup of the data
directory. But when you do the physical b
On Thu, 26 Jan 2006, Tom Lane wrote:
That's got the wrong ownership (should be postgres not root)
Tom,
I wondered about that.
and the wrong permissions (should be world-writable). Did somebody do
something silly like chown everything in /tmp?
Not me ... intentionally.
You could manu
looks like perl/DBD::Pg is looking for libpq.so.3 but postgresql 8.1.X supplies
libpq.so.4. You need to rebuild DBD::Pg
to get this to work (atleast that is what I have been doing for my upgrades
from 7.4.X to 8.1.2)
Jim
-- Original Message ---
From: Rich Shepard <[EMAIL PROT
I am not sure what to do on this. Right now we have a one-line test:
AC_REPLACE_FUNCS([getaddrinfo])
To test for a macro we are going to need to add include netdb.h, and the
LINK test below is overkill. I am thinking we should just hard-code in
HAVE_GETADDRINFO for the True64 platform; an
Rich Shepard <[EMAIL PROTECTED]> writes:
> install_driver(Pg) failed: Can't load
> '/usr/lib/perl5/site_perl/5.8.7/i486-linux/auto/DBD/Pg/Pg.so' for module
> DBD::Pg: libpq.so.3: cannot open shared object file: No such file or
> directory at /usr/lib/perl5/5.8.7/i486-linux/DynaLoader.pm line 230
I didn't read your mail very carefully, but I guess you want:
- turn on WAL archiving, and archive all WAL logs;
- take the file system backup at regular time points, optionally you
can keep them also for point in time recovery;
Then you always have all the WAL files you need to recover to an
Um, no you didn't read my email at all. I am aware of all of that
and it is clearly outlined in the docs. My email was about a
specific detail in the process. Please read it if you want to know
what my actual question was.
Thanks,
Rick
On Jan 26, 2006, at 10:41 AM, Csaba Nagy wrote:
On Thu, 26 Jan 2006, Jim Buttafuoco wrote:
looks like perl/DBD::Pg is looking for libpq.so.3 but postgresql 8.1.X
supplies libpq.so.4. You need to rebuild DBD::Pg to get this to work
(atleast that is what I have been doing for my upgrades from 7.4.X to
8.1.2)
Jim,
I thought I had mentioned
I am looking for suggestions on storing and retrieving geocode
information.
My application currently stores 2 columns (lat, long) as numeric and I
have a btree index on them. This works fine for the current set of
data, but as it expands I know it will become an issue.
I am looking at changing t
On Thu, 26 Jan 2006, Rich Shepard wrote:
What do I do to trace the source of this problem and fix it?
Thanks to Jim I found that libpq.so.3 were in the old directory. As soon as
I moved them to /usr/lib (with libpq.so.4), SQL-Ledger allowed me to log in.
All of this reminds me of the tim
Hi,
I am upgrading from 7.4.8 -> 8.1.2 on Linux 2.6.14.3 #1 SMP
I have installed 8.1.2 and created the database (with encoding 'UNICODE', as
I had done in 7.4.8) and am trying to load a 7.4.8 dump file but I am
getting a few errors like this:
psql:bugasbase2-backup:45880: ERROR: invalid UTF-8 b
On Thu, Jan 26, 2006 at 12:55:46PM -0500, George Woodring wrote:
> I am looking for suggestions on storing and retrieving geocode
> information.
Consider using PostGIS:
http://www.postgis.org/
--
Michael Fuhr
---(end of broadcast)---
TIP 3: Have
Adam Witney wrote:
> psql:bugasbase2-backup:45880: ERROR: invalid UTF-8 byte sequence detected
> near byte 0xb5
> CONTEXT: COPY array_scheme, line 17560, column gene_identifier: "[EMAIL
> PROTECTED]
> (0G11)"
>
> This dump file will load error free into 7.4.8.
>
> Does anybody have any ideas w
I would like to make a table of 20 plus columns the
majority of columns being arrays.
The following test works. The array will hold up to
five characteristics of each parameter including the unit of measurement used.
Using traditional methods I would need six columns to accomplish the same
Here, it was the move from /usr/local/pgsql to /var/lib/pgsql that caused
me all this grief.
A huge "thank you" to all of you -- and especially Jim.
Although I am glad you were able to get up and running, typically you
don't want to "move" libs like that. Instead update your /etc/ld.so.c
I want to implement nest transactions like
begin;
CREATE temp table t2 (foo char(20) primary key);
begin;
CREATE temp table t1 (bar char(20) primary key);
commit;
rollback;
I'm expecting that t1 and t2 tables are not created since last rollback
rolls back its nested transaction.
H
On Thu, 26 Jan 2006, Joshua D. Drake wrote:
Although I am glad you were able to get up and running, typically you don't
want to "move" libs like that. Instead update your /etc/ld.so.conf and run
ldconfig.
True, Josh. What I'd prefer to do is remove /usr/local/pgsql/ once I know
that nothing
Bruce Momjian writes:
> I am not sure what to do on this. Right now we have a one-line test:
> AC_REPLACE_FUNCS([getaddrinfo])
> To test for a macro we are going to need to add include netdb.h, and the
> LINK test below is overkill. I am thinking we should just hard-code in
> HAVE_GETADDRINF
Rich Shepard <[EMAIL PROTECTED]> writes:
> On Thu, 26 Jan 2006, Joshua D. Drake wrote:
>
>> Although I am glad you were able to get up and running, typically you don't
>> want to "move" libs like that. Instead update your /etc/ld.so.conf and run
>> ldconfig.
>
>True, Josh. What I'd prefer to d
On Thu, Jan 26, 2006 at 10:15:22AM -0800, Bob Pawley wrote:
> I would like to make a table of 20 plus columns the
> majority of columns being arrays.
>
> The following test works. The array will hold up to five
> characteristics of each parameter including the unit of
> measurement used. Using tra
"Andrus" <[EMAIL PROTECTED]> writes:
> I want to implement nest transactions like
> begin;
> CREATE temp table t2 (foo char(20) primary key);
> begin;
> CREATE temp table t1 (bar char(20) primary key);
> commit;
> rollback;
That is not the correct syntax. Use SAVEPOINT, then ROLLBAC
Bob Pawley <[EMAIL PROTECTED]> writes:
> insert into specifications values ('1', '{25, 50, 100, gpm}', '{{100, 250,
> 500, DegF}}',
> '{{{10, 40, 100, psi}}}', '60, 120, 150, psi' );
Why are you putting in all those extra braces?
regards, tom lane
Because it gives me an error otherwise.
I am following the rules layed out in the documentation as follows -
Bob
8.10.2. Array Value Input
Now we can show some INSERT statements.
INSERT INTO sal_emp
VALUES ('Bill',
'{1, 1, 1, 1}',
'{{"meeting", "lunch"}, {"meetin
Tom Lane wrote:
> Bruce Momjian writes:
> > I am not sure what to do on this. Right now we have a one-line test:
> > AC_REPLACE_FUNCS([getaddrinfo])
> > To test for a macro we are going to need to add include netdb.h, and the
> > LINK test below is overkill. I am thinking we should just hard
Bruce Momjian writes:
> I have the answer. Tru64 netdb.h has:
> #if defined (_SOCKADDR_LEN) || defined (_XOPEN_SOURCE_EXTENDED)
> #define getaddrinfo ngetaddrinfo
> #else
> #define getaddrinfo ogetaddrinfo
> #endif
Seems like the same method we use for testing fini
I second that, and I'd love to have someone clarify the appropriate
time to use arrays vs. more columns or an referenced tabled. I've
always found that confusing.
Thanks,
Eric
Karsten Hilbert wrote:
And why would that be undesirable ?
On Thu, Jan 26, 2006 at 10:15:22AM -0800, Bob Pawley
- Original Message -
From: "Bob Pawley" <[EMAIL PROTECTED]>
To: "Karsten Hilbert" <[EMAIL PROTECTED]>
Sent: Thursday, January 26, 2006 11:26 AM
Subject: Re: [GENERAL] Arrays
Because with arrays I can include other information such as pointers to
conversion factors and hopefully imple
I second that, and I'd love to have someone clarify the appropriate time
to use arrays vs. more columns or an referenced tabled. I've always
found that confusing.
Thanks,
Eric
Karsten Hilbert wrote:
And why would that be undesirable ?
On Thu, Jan 26, 2006 at 10:15:22AM -0800, Bob Pawley wr
On Thu, 26 Jan 2006, Bob Pawley wrote:
> Because it gives me an error otherwise.
What error?
insert into specifications values ('1', '{25, 50, 100, gpm}',
'{100, 250, 500, DegF}',
'{10, 40, 100, psi}', '{60, 120, 150, psi}' );
seems to insert fine for me given the table definition you gave.
>
why not just use setval(), see docs for arguments.
I think that "setval('seq_name', xx)" have the same effect than
"SEQUENCE seq_name RESTART WITH xx" (the instruction I
wanted to use in my first function).
But the problem is that in both cases, the sequence should be
locked in order to preven
We have 2 tables we expect to grow by up to
50,000 rows per day each depending on the customer. In normal
operation we will most likely never update or delete from these tables
as they are for historical reporting. (Eventually we may but a limit
on the amount of data and delete older than X
ERROR: malformed array literal: "{100, 250, 500, DegF)"
I want to do single dimension arrays.
How did I turn it into multidmensional?
Bob
- Original Message -
From: "Stephan Szabo" <[EMAIL PROTECTED]>
To: "Bob Pawley" <[EMAIL PROTECTED]>
Cc: "Tom Lane" <[EMAIL PROTECTED]>; "Postgre
ERROR: malformed array literal: "{100, 250, 500, DegF)"
I want to do single dimension arrays.
How did I turn it into multidmensional?
Bob
- Original Message -
From: "Stephan Szabo" <[EMAIL PROTECTED]>
To: "Bob Pawley" <[EMAIL PROTECTED]>
Cc: "Tom Lane" <[EMAIL PROTECTED]>; "Postgresq
Bob Pawley <[EMAIL PROTECTED]> writes:
> ERROR: malformed array literal: "{100, 250, 500, DegF)"
You wrote a right paren, not a right brace ...
> I want to do single dimension arrays.
> How did I turn it into multidmensional?
The multiple levels of braces create a multidimensional array.
Bob Pawley wrote:
ERROR: malformed array literal: "{100, 250, 500, DegF)"
Well you have a typo:
"{100, 250, 500, DegF)" is wrong...
"{100, 250, 500, DegF}" is correct...
Sincerely,
Joshua D. Drake
--
The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
PostgreSQL Replication, Consu
> That is not the correct syntax. Use SAVEPOINT, then ROLLBACK TO SAVEPOINT
> or RELEASE SAVEPOINT.
postgres log file:
2006-01-26 21:45:59 LOG: statement: INSERT INTO dok .
2006-01-26 21:45:59 ERROR: insert or update on table "dok" violates foreign
key constraint "dok_klient_fkey"
2006-01
If you really are just inserting, and never updating or deleting, then you
will never need to vacuum the table, rather you will just need to ANALYSE
the table. If you use autovacuum that is exactly what it will do.
As for Reindex, I'm not entirely sure, I don't think you would benefit
from reinde
Thank you - my eyes aren't what they used to be.
Bob
- Original Message -
From: "Joshua D. Drake" <[EMAIL PROTECTED]>
To: "Bob Pawley" <[EMAIL PROTECTED]>
Cc: "Stephan Szabo" <[EMAIL PROTECTED]>; "Tom Lane"
<[EMAIL PROTECTED]>; "Postgresql"
Sent: Thursday, January 26, 2006 12:20 PM
I missed that - thanks for the help.
Bob
- Original Message -
From: "Tom Lane" <[EMAIL PROTECTED]>
To: "Bob Pawley" <[EMAIL PROTECTED]>
Cc: "Stephan Szabo" <[EMAIL PROTECTED]>; "Postgresql"
Sent: Thursday, January 26, 2006 12:12 PM
Subject: Re: [GENERAL] Arrays
Bob Pawley <[EMAI
Joshua D. Drake schrieb:
> Bob Pawley wrote:
>
>> ERROR: malformed array literal: "{100, 250, 500, DegF)"
>
>
> Well you have a typo:
>
> "{100, 250, 500, DegF)" is wrong...
>
> "{100, 250, 500, DegF}" is correct...
>
I'd say both are wrong ;)
'{100,250,500,DegF}' could work. But I'm not sur
On Thu, Jan 26, 2006 at 02:35:42PM -0500, Matthew T. O'Connor wrote:
> If you really are just inserting, and never updating or deleting, then you
> will never need to vacuum the table, rather you will just need to ANALYSE
> the table.
That's not quite true; the table must still be vacuumed occasio
The order for the array is Min, Norm, Max, Unit.
I'll probably reorder it with the unit first as every value has a unit.
Bob
- Original Message -
From: "Tino Wildenhain" <[EMAIL PROTECTED]>
To: "Joshua D. Drake" <[EMAIL PROTECTED]>
Cc: "Bob Pawley" <[EMAIL PROTECTED]>; "Stephan Szabo
Bob Pawley schrieb:
> The order for the array is Min, Norm, Max, Unit.
>
> I'll probably reorder it with the unit first as every value has a unit.
>
I'd rather create/use a custom datatype for your needs.
This array stuff seems overly hackish for me.
Regards
Tino
---(en
Outside of "VACUUM FREEZE", is there any way the "xmin" column in a
relation can change, assuming of course the tuple is never updated
again? I'm considering using this as a way to identify all tuples
modified in the same transaction (in an effort to group them
together), and am wondering
Michael Fuhr <[EMAIL PROTECTED]> writes:
> On Thu, Jan 26, 2006 at 02:35:42PM -0500, Matthew T. O'Connor wrote:
>> If you really are just inserting, and never updating or deleting, then you
>> will never need to vacuum the table, rather you will just need to ANALYSE
>> the table.
> That's not quit
"Eric B. Ridge" <[EMAIL PROTECTED]> writes:
> Outside of "VACUUM FREEZE", is there any way the "xmin" column in a
> relation can change, assuming of course the tuple is never updated
> again?
If the tuple lives long enough, VACUUM will change it to FrozenTransactionId
eventually, even without
On Thu, Jan 26, 2006 at 04:19:34PM -0500, Eric B. Ridge wrote:
> Outside of "VACUUM FREEZE", is there any way the "xmin" column in a
> relation can change, assuming of course the tuple is never updated
> again? I'm considering using this as a way to identify all tuples
> modified in the same
Our application will be dispersed amongst many users.
I want to keep the datbase as generic as possible.
Bob
- Original Message -
From: "Tino Wildenhain" <[EMAIL PROTECTED]>
To: "Bob Pawley" <[EMAIL PROTECTED]>
Cc: "Joshua D. Drake" <[EMAIL PROTECTED]>; "Stephan Szabo"
<[EMAIL PROTE
matthew@zeut.net ("Matthew T. O'Connor") writes:
> If you really are just inserting, and never updating or deleting,
> then you will never need to vacuum the table, rather you will just
> need to ANALYSE the table. If you use autovacuum that is exactly
> what it will do.
"Never" is a pretty long
On Jan 26, 2006, at 4:44 PM, Tom Lane wrote:
"Eric B. Ridge" <[EMAIL PROTECTED]> writes:
Outside of "VACUUM FREEZE", is there any way the "xmin" column in a
relation can change, assuming of course the tuple is never updated
again?
If the tuple lives long enough, VACUUM will change it to
Fro
On Jan 26, 2006, at 4:50 PM, Michael Fuhr wrote:
test=> SELECT xmin, * FROM foo;
xmin | x
+---
424584 | 1
424585 | 2
424584 | 3
(3 rows)
hmm. Is it possible to grab that first xmin value when the
transaction first starts, then I can explicitly use when I need it?
eric
--
"Eric B. Ridge" <[EMAIL PROTECTED]> writes:
> That's what I was afraid of. I've pondering making a "grouping"
> column that gets set to "xmin" via an UPDATE trigger. At least I'd
> have a constant value that would survive database dumps and reloads.
That will most assuredly NOT work. You wi
On Thu, Jan 26, 2006 at 05:05:19PM -0500, Eric B. Ridge wrote:
> I really need a way to create a unique identifier at the start of a
> top-level transaction, and be able to use it via triggers and/or
> column default values in that or its subtransactions.
I suppose a sequence is out of the que
On Thu, Jan 26, 2006 at 03:22:50PM -0700, Michael Fuhr wrote:
> On Thu, Jan 26, 2006 at 05:05:19PM -0500, Eric B. Ridge wrote:
> > Is there some kind of "TopXID" magic variable/function that I haven't
> > found in the documentation?
>
> Not in the standard installation, but I think a C function
I can't imagine
test=# create type stat1 as (i1 int, i2 int, i3 int, t1 text);
CREATE TYPE
test=# create table stest(s1 stat1);
CREATE TABLE
test=# insert into stest values ((1,1,1,'t'));
INSERT 0 1
test=# select * from stest;
s1
---
(1,1,1,t)
(1 row)
being a big issue. You've got
hi,
I found the following function on http://archives.free.net.ph/message/20050613.063258.1a326e27.en.html.
When i run it on PostgreSQL8.0.1 (on fedora core 2), i get the error:
dbm=# select * from excpt_test();
ERROR: syntax error at or near "sqlstate" at character 133
QUERY:
begin
begin
On Jan 27, 2006, at 4:41 , Eric E wrote:
I second that, and I'd love to have someone clarify the appropriate
time to use arrays vs. more columns or an referenced tabled. I've
always found that confusing.
I would only use arrays if the natural data type of the data is an
array, such as s
On Thu, Jan 26, 2006 at 03:02:46PM -0800, vishal saberwal wrote:
> When i run it on PostgreSQL8.0.1 (on fedora core 2), i get the error:
>
> dbm=# select * from excpt_test();
> ERROR: syntax error at or near "sqlstate" at character 133
SQLSTATE and SQLERRM are new in 8.1; they're not available i
oh thanks,i didnt know that,highly appreciate your help and quick response ...vishOn 1/26/06, Michael Fuhr <
[EMAIL PROTECTED]> wrote:On Thu, Jan 26, 2006 at 03:02:46PM -0800, vishal saberwal wrote:
> When i run it on PostgreSQL8.0.1 (on fedora core 2), i get the error:>> dbm=# select * from excpt_
On Jan 26, 2006, at 5:22 PM, Michael Fuhr wrote:
I suppose a sequence is out of the question? Too easy to get it
wrong?
Well, I just wanted to avoid embedding this idea into my
application. Would rather Postgres take care of it for me.
Not in the standard installation, but I think a C fu
Thanks Scott - I'll give this a try.
Bob
- Original Message -
From: "Scott Marlowe" <[EMAIL PROTECTED]>
To: "Bob Pawley" <[EMAIL PROTECTED]>
Cc: "Tino Wildenhain" <[EMAIL PROTECTED]>; "Joshua D. Drake"
<[EMAIL PROTECTED]>; "Stephan Szabo" <[EMAIL PROTECTED]>; "Tom
Lane" <[EMAIL PROTE
Now that I have postgres-8.1.2 properly configured and running I wanted to
create a new database for an application. Postgres would not let me -- as a
user -- create the database, so I su'd to 'postgres'.
As user 'postgres' I could invoke psql and tried to create the database
with the command
On Jan 27, 2006, at 10:54 , Rich Shepard wrote:
As user 'postgres' I could invoke psql and tried to create the
database
with the command, 'create database contacts username=rshepard'.
That failed
with no error message.
Could you provide a sample session, from login to psql to logout? Th
On Thu, 26 Jan 2006, Rich Shepard wrote:
>Now that I have postgres-8.1.2 properly configured and running I wanted to
> create a new database for an application. Postgres would not let me -- as a
> user -- create the database, so I su'd to 'postgres'.
>
>As user 'postgres' I could invoke p
On Fri, 27 Jan 2006, Michael Glaesemann wrote:
Could you provide a sample session, from login to psql to logout? The added
information may give someone on the list more insight into what's going
wrong.
Michael,
Sure:
[EMAIL PROTECTED] ~]$ su postgres
Password:
[EMAIL PROTECTED]:/home/rsh
On Thu, 26 Jan 2006, Stephan Szabo wrote:
Did you put a semicolon at the end of the command? I get a
ERROR: syntax error at or near "username" at character 26
LINE 1: create database contacts username=sszabo
Stephan,
No, I did not put a semicolon there. I also received no error message, j
On Jan 27, 2006, at 11:22 , Rich Shepard wrote:
postgres=# create database testcase
postgres-# \q
I think Stephan's right: you need to end the statement with a semi-
colon (or \g in psql).
Michael Glaesemann
grzm myrealbox com
---(end of broadcast)--
On Thursday 26 January 2006 19:24, Rich Shepard wrote:
> On Thu, 26 Jan 2006, Stephan Szabo wrote:
> > Did you put a semicolon at the end of the command? I get a
> > ERROR: syntax error at or near "username" at character 26
> > LINE 1: create database contacts username=sszabo
>
> Stephan,
>
>
On Thu, 26 Jan 2006, Rich Shepard wrote:
> On Thu, 26 Jan 2006, Stephan Szabo wrote:
>
> > Did you put a semicolon at the end of the command? I get a
> > ERROR: syntax error at or near "username" at character 26
> > LINE 1: create database contacts username=sszabo
>
> Stephan,
>
>No, I did
On Fri, 27 Jan 2006, Michael Glaesemann wrote:
I think Stephan's right: you need to end the statement with a semi-colon (or
\g in psql).
Sigh. Of course. By the time I got to this point I had put in a rather full
day and was not thinking clearly.
Apologies all around,
Rich
--
Richard B. S
> Also, somebody made a real good point about rolled-back insertions.
> Even if the only command you ever apply to the table is INSERT, you
> could still have dead rows in the table if some of those transactions
> occasionally roll back.
hmm... That's true. I don't think autovacuum doesn't anythi
On Thu, Jan 26, 2006 at 18:24:36 +0100,
LaroG <[EMAIL PROTECTED]> wrote:
> Hey.
> I am new here. I’m from Poland:-)
> I have one question (I don’t now if this is the right group for this question
> and … if my English is enough good… :P):
> Are the developers going to implement some system trig
On Thu, Jan 26, 2006 at 12:55:46 -0500,
George Woodring <[EMAIL PROTECTED]> wrote:
> I am looking for suggestions on storing and retrieving geocode
> information.
>
> My application currently stores 2 columns (lat, long) as numeric and I
> have a btree index on them. This works fine for the cur
1 - 100 of 104 matches
Mail list logo
