On 3/17/07, louis gonzales <[EMAIL PROTECTED]> wrote:
Statement-level triggers follow simple visibility rules: none of the changes
made by a statement are visible to statement-level triggers that are invoked
before the statement, whereas all modifications are visible to
statement-level after trig
On 3/18/07, Mageshwaran <[EMAIL PROTECTED]> wrote:
Hi,
In our company there are many postgres servers in 7.X version,we are in
the process of upgrading to 8.1 version, can anyone tell me the
method to do this upgradation.
http://www.postgresql.org/docs/faqs.FAQ.html#item3.6
Btw, I personally f
Hi,
In our company there are many postgres servers in 7.X version,we are in
the process of upgrading to 8.1 version, can anyone tell me the
method to do this upgradation.
Regards
J Mageshwara
DBA
** DISCLAIMER **
Information contained and transmitted by this E-MAIL is proprie
louis gonzales escribió:
> louis gonzales wrote:
>
> >2) Seeing as you have no idea - not attacking, stating fact - on the
> >rationale behind the "insert statement-level" to create 1-to-1 table
> >for each statement-level
> >insert, I'd say your presumption is unfounded.
This won't work anyway
louis gonzales wrote:
Dear Hubert,
Two things
1) _*"statement-level" and "row-level" straight from PostgreSQL:
http://www.postgresql.org/docs/8.1/interactive/trigger-datachanges.html*_
*
_*Statement-level triggers*_ follow simple visibility rules:
none of the changes made by a
Bob Hartung wrote:
> Thanks, but I have these changes in and it still will not connect:
> file: pg_hba.conf:
> # IPv4 local connections:
> hostall all 127.0.0.1/32 ident sameuser
He also wrote:
> >>$db = pg_connect('dbname=bpsimple user=minitwr password=RWHart') ;
T
On Sun, 2007-03-18 at 00:40 +0530, Mageshwaran wrote:
> how to find the size of a particular database in postgres...
The old way was to use du or similar. Recent versions (I believe >=8.1,
but check the release notes to be sure) provide several useful functions
for this:
pg_column_size
pg_databa
Thanks, but I have these changes in and it still will not connect:
file: pg_hba.conf:
# IPv4 local connections:
hostall all 127.0.0.1/32 ident sameuser
postgrsql.conf:
listen_addresses = 'localhost'
port = 5432
It is my understanding that the current ver
Alain Roger wrote:
> insert into immense.statususer (statususer_id, statususer_type) values
> (SELECT nextval( 'statususer_statususer_id_seq' ),'customer');
The correct syntax would be:
insert into immense.statususer (statususer_id, statususer_type) values
((SELECT nextval( 'statususer_statususer_
For small and moderate size databases, I find that the simplest way to
estimate the database size is to do:
du -ks /var/lib/postgresql/data
...create a new database, restore a backup of the database in whose
size you're interested in
du -ks /var/lib/postgresql/data
Compare the first and second "
Dear Hubert,
Two things
1) "statement-level" and "row-level" straight from PostgreSQL:
http://www.postgresql.org/docs/8.1/interactive/trigger-datachanges.html
Statement-level triggers follow simple visibility
rules: none of the changes made by a statement are visible to
statement-level
Mageshwaran schrieb:
Hi all,
how to find the size of a particular database in postgres...
You look there:
http://www.postgresql.org/docs/8.2/static/storage-file-layout.html
and use OS commands to calculate space used on disk (e.g. du)
please do reply
Well, thats a mailinglist, why would
Jonathan Vanasco <[EMAIL PROTECTED]> writes:
> However-- explain doesn't pull in the planner's scanning info in
> regards to the fkey constraints. is there any function or argument
> that will ?
Not directly --- but in reasonably recent PG versions, EXPLAIN ANALYZE
shows the runtime for trigg
Hi,
I would like to auto increment my sequence when i'm going to insert a new
record into my table.
for that i wanted to use :
insert into immense.statususer (statususer_id, statususer_type) values
(SELECT nextval( 'statususer_statususer_id_seq' ),'customer');
however, i get an error message i
Hi all,
how to find the size of a particular database in postgres...
please do reply
Regards
J Mageshwaran
DBA
** DISCLAIMER **
Information contained and transmitted by this E-MAIL is proprietary to
Sify Limited and is intended for use only by the individual or entity to
w
Hello,
I'm working a lot with psql and plpgsql, I have a project based on psql and
for the developpement I often need to "dump" a function, it is not really
possible with psql because you don't have correctly the parameter.
So I've made a patch for pg_dump which permit to dump all the functions
I've got a DELETE query that takes ~2 seconds to process
The reasoning is simple -- its doing referential checks, to make sure
that I'm not deleting a valid fkey , as several tables fkey on that
one.
The issue i'm running into is obvious: this should not take 2
seconds. anything that f
Richard Broersma Jr wrote:
what i need is to see how 2 fields specific change there values, to do
that i plan to make a temporal table with the fields before and after
plus the time the changes where made... can i do this with store
procedures??
http://www.varlena.com/varlena/GeneralBits
> what i need is to see how 2 fields specific change there values, to do
> that i plan to make a temporal table with the fields before and after
> plus the time the changes where made... can i do this with store
> procedures??
http://www.varlena.com/varlena/GeneralBits/104.php
Check out this d
Hello.
I been having "problems" with and application, and i want to store in
the data base the changes(update) made to a specific table.
what i need is to see how 2 fields specific change there values, to do
that i plan to make a temporal table with the fields before and after
plus the time the
On 3/16/07, Dmitry Koterov <[EMAIL PROTECTED]> wrote:
Overall, we need 3 roles:
1. Administrator: can do anything with a database (by default this user is
already exists - "postgres").
2. Read-only: can only read. Runs on all slave nodes.
actually - you dont need the read-only role, if this is
On Sat, Mar 17, 2007 at 01:47:11AM +0300, Dmitry Koterov wrote:
> When we start using of any replication system (e.g. Slony) we need to create
> a "read-only" role for access the database. This role must be able to read
> anything, but should NOT be able to INSERT, UPDATE or DELETE for all
> datab
Thank you for your tips. I think I will change the tables and use some
minimal date instead of a null value to represent a constraint that is
valid all the time. An additional advantage of this approach is that I
can then make sure that the time intervals (I not only have a start
date, but also an
23 matches
Mail list logo
