On Wed, 2003-07-30 at 15:26, Tom Lane wrote:
Mendola Gaetano [EMAIL PROTECTED] writes:
John P. Looney [EMAIL PROTECTED] writes:
bbadmin | | SQL_ASCII
For sure a way to obtain this inconsistence is delete the owner of
a db and voila' a DB result to have no owner.
[EMAIL PROTECTED] writes:
sorry, when i referred to disk space used i meant the actual amount
used by live rows. if i insert 1000 rows then delete 999 of them, the
disk file will be the size of the 100 row container (make that 1000, not
100 - i cannot backspace here) until i do a vacuum full
Hey guys, one of my servers is running Red Hat 7.3, what's my best bet
for upgrading? Rebuild from postgresql-7.3.4-1PGDG.src.rpm? Rebuild from
postgresql-7.3.4-1PGDG.rh73.src.rpm in the aurora directory? Will
someone be submitting a 73 rpm for redhat 7.3 / i386 ? THanks in
advance,
Robert Treat
On Thu, 31 Jul 2003, Peter Eisentraut wrote:N
[EMAIL PROTECTED] writes:N
sorry, when i referred to disk space used i meant the actual amount
used by live rows. if i insert 1000 rows then delete 999 of them, the
disk file will be the size of the 100 row container (make that 1000, not
100
On Thu, Jul 31, 2003 at 08:51:09AM -0400, [EMAIL PROTECTED] wrote:
well, i can admit that i am confused. my assumption is that when a row
is deleted in pg, that row is merely marked as 'gone' until a vacuum-full
is done. my further assumption is that if i continue to add rows, those
rows are
Thanks very much!!
I had a user who was allowed to create dbs, but wasn't superuser...Now I
just have a superuser.
Benjamin
Devrim GUNDUZ wrote:
Hi,
On Tue, 29 Jul 2003, Benjamin Thelen (CCGIS) wrote:
I would like to change the ownership of a database. The only thing I
could find up to now,
Hello all,
I currently have a project which will store roughly 10B records in
postgres which will be inserted at a rate of about 40K/s. While we have
adequate disk storage it is paramount that subsets of the data be
queryable quickly, without hindering the insert process to a crawl.
On Thu, 31 Jul 2003, Andrew Sullivan wrote:
On Thu, Jul 31, 2003 at 08:51:09AM -0400, [EMAIL PROTECTED] wrote:
well, i can admit that i am confused. my assumption is that when a row
is deleted in pg, that row is merely marked as 'gone' until a vacuum-full
is done. my further assumption
On Thu, Jul 31, 2003 at 01:41:54PM -0400, [EMAIL PROTECTED] wrote:
well, i was close. i didn't realize that i had to do a (non-full)
vacuum to mark deleted space as free.
Ooops, I think I was still unclear. VACUUM FULL actually re-arranges
the file, and returns it to the filesystem. Plain
pg_dump -h server -Of ./temp.dmp -u username END
username
password
END
-- I've been trying to use this command and have always been able to
successfully dump my database via scripts. Now, it prompts me despite this
standard input value, or any other one. It just waits for me to enter
Mike Miller [EMAIL PROTECTED] writes:
pg_dump -h server -Of ./temp.dmp -u username END
username
password
END
This worked until I upgraded to 7.3.3 from 7.1.3. Any ideas why this would
happen and how to work around it to get automatic scriped dumps?
This is a deliberate change for
I installed PostgreSQL 7.3.4 on Red Hat Linux 8.0.
When I tried to mount database (using initdb command), following error appear:
You cannot run initdb as root. Please log in as the (unprivileged) user that
will own the server process.
I read at Postgre documentation, and I need to log on as
You don't have to LOGOUT and LOGIN again as another user,
youjustdo: # su user
#su postgres
The postgresmust exist and this is who will own the database.
Regards,
MAGO
---Mensaje original---
De: Daniel Gerardo Lucero Baylon
Fecha: Jueves, 31 de Julio de 2003 05:03:08 p.m.
A:
Greetings!
I'm a new (very new) postgresql dba, and I was
wondering if the following error messages
are 'Normal' in your environments.
I've already gone into single user mode and
issued 'reindex database dbname', yet these
messages still persist.
Thanks in advance for any help or tips you
I'm playing with redhat 9.0 which is postgresql 7.3..2
I set my date style like I have on previous releases to ISO the time
stamps show up in ISO format, but with out time zone info?
is this going to be the default going forward from 7.3.2, is this just
somthing temporary, should I just pick
Hi,
Either we have found a bug in Postgres (which I seriously doubt) or we
are being stupid clever enough way to not notice it.
We have five complex transactions that are executed thru pq++/c++
interface. If we run them one by one everything goes fine. But if I
run them in parallel - in separate
I installed PostgreSQL 7.3.4 on a red Hat Linux 8.0 system.
When I try to install clusters using initdb and postmaster commands to start
server and database, an error occurs:
You cannot run initdb -D /usr/local/pgsql/data as root. Please log in as the
(unprivileged) user that will own the server
In response to Mendola Gaetano:
I'm running Postgres7.3.3 and I'm performing this simple select:
Looking at your fast three step plan
SELECT id_class from class_default where id_provider = 39;
SELECT id_user from user_data where id_class in ( 48 );
SELECT * from user_logs where id_user in (
What's up here ? Google is deathly silent.
bash-2.05a$ pg_dumpall db.out
connected to template1...
dumping database MyPgSQLTest...
dumping database bb1...
dumping database bbadmin...
pg_dump: [archiver (db)] connection to database bbadmin failed: FATAL
1: SetDatabaseEncoding(): invalid
Priya Nair would like to recall the message, help needed for performance tuning.
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
Hi:
I notice the following error message in my
postgresql log file:
FATAL : s_lock (0x401db020) at lwlock.c Stuck
spinlock. Aborting
Version of my postgresql :
PostgreSQL 7.2.3 on i686-pc-linux-gnu compiled by
GCC 2.96
Operating System : RedHat 7.1
What can cause a stuck
Title: iColony - Departamento de Projetos
Paulo FabrÃcio Puga
MirandaDesenvolvimento de TIfabricio
@icolony.com.br(31) 9691-3494
On 31 Jul 2003, Mauri Sahlberg wrote:
Either we have found a bug in Postgres (which I seriously doubt) or we
are being stupid clever enough way to not notice it.
We have five complex transactions that are executed thru pq++/c++
interface. If we run them one by one everything goes fine. But
There are two interfaces that I know of.
1) pgAdmin II is a windows based interface to postgress but they
already have a alpha code for pgAdmin III wich will work on unix and
other platforms. http://www.pgadmin.org
2) phpPgAdmin which is a web based interface to postgres done in php.
Very
Arno A. Karner [EMAIL PROTECTED] writes:
I'm playing with redhat 9.0 which is postgresql 7.3..2
I set my date style like I have on previous releases to ISO the time
stamps show up in ISO format, but with out time zone info?
timestamp now means timestamp without time zone, per SQL spec.
You
Ludwig Isaac Lim [EMAIL PROTECTED] writes:
What can cause a stuck spinlock?
In theory, that shouldn't ever happen. Can you reproduce it?
regards, tom lane
---(end of broadcast)---
TIP 4: Don't 'kill -9' the
Ok me dumb, I've spend copple days editing my table definintions from
Dlm DATETIME NOT NULL DEFAULT TEXT 'now'
Dlm = date time last modified to
Dlm timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP
which from my previous post I was told should be
Dlm timestamptz NOT NULL DEFAULT
Shankar,
Is there a better way to do this. comments are
appreciated.
No. This is one of the major features in 7.4; FSM and VACUUM will manage
indexes as well. Until then, we all suffer
BTW, the REINDEX command is transaction-safe. So if your database has lull
periods, you can run
Hi,
1. Please post performance related questions to
[EMAIL PROTECTED] for better
response.
2. Please try to give as much information as possible in
first place itself , eg
a) you have not told what the query is
b) what is the explain analyze output of the query ( explain analyze
query )
c)
previous table definition guess no not null of default ''
curreent table definitionCREATE TABLE apps
(
Id int not null unique,-- AppId
Sym varchar(8) not null default '', -- app symbol name
Nam varchar(30) not null default '',-- app full name
BitPriv varchar(10) not null
On pe, 2003-08-01 at 03:12, Stephan Szabo wrote:
interface. If we run them one by one everything goes fine. But if I
run them in parallel - in separate processes - all but the first one
claiming the lock for ryhmalaiset-table will fail. And they will
fail as soon as the first one is
On 1 Aug 2003, Mauri Sahlberg wrote:
On pe, 2003-08-01 at 03:12, Stephan Szabo wrote:
interface. If we run them one by one everything goes fine. But if I
run them in parallel - in separate processes - all but the first one
claiming the lock for ryhmalaiset-table will fail. And they
On Thu, 31 Jul 2003, maillist wrote:
select * from apps where (not apppag = null);
returns nothing when it should return every thing
No. It should return nothing. apppag = null returns unknown for every
row. Use IS NULL to test if a value is null.
---(end of
On pe, 2003-08-01 at 08:51, Stephan Szabo wrote:
On 1 Aug 2003, Mauri Sahlberg wrote:
On pe, 2003-08-01 at 03:12, Stephan Szabo wrote:
interface. If we run them one by one everything goes fine. But if I
run them in parallel - in separate processes - all but the first one
claiming
34 matches
Mail list logo
