Tom Lane wrote:
Bernhard D Rohrer [EMAIL PROTECTED] writes:
I have a broken database and not much clue about postgres, sorry for the
n00b questions :(
I think you've got a cross-version problem, as in the database is really
PG 8.0 or earlier but you're trying to run 8.1 against it. What is
Guillaume Lelarge wrote:
We first send the query to the database. For each returned column, we
send two queries. The first one gives us the type's name of the column
and the second one gives us the OID of the base type. So, each query
executed with pgAdmin's query tool should increase
Alvaro Herrera wrote:
Guillaume Lelarge wrote:
We first send the query to the database. For each returned column, we
send two queries. The first one gives us the type's name of the column
and the second one gives us the OID of the base type. So, each query
executed with pgAdmin's query tool
Postgres admin team,
I posed this question last week. Probably a bad week to ask questions as
many people off
For the holidays so response was light. Thanks to Pete Eisentraut for his
feedback.
I'd like to pose the question again. Our upgrade time-table is getting
close. Any and
All
Greetings and Salutations...
This has probably been discussed a number of times, but I really need
your help. I am upgrading from 8.1 to 8.2. Right now I have the
restore of the database to the new version running. It has been
running since December 21, at 4:30 PM. I'm in a University
On Jan 2, 2008 9:34 AM, Carol Walter [EMAIL PROTECTED] wrote:
Greetings and Salutations...
This has probably been discussed a number of times, but I really need
your help. I am upgrading from 8.1 to 8.2. Right now I have the
restore of the database to the new version running. It has been
Hi Carol,
On Wed, Jan 02, 2008 at 10:34:47AM -0500, Carol Walter wrote:
This has probably been discussed a number of times, but I really need
your help. I am upgrading from 8.1 to 8.2. Right now I have the
restore of the database to the new version running. It has been
running since
Hello,
I have upgraded from postgreSQL version 7.3.6 to 8.2.4 few days ago.
Everything works perfectly, but I have strange problem with backup.
My database contains blob's, but i was not doing backup with blobs every
day. I am doing daily backup with command : pg_dump -U user_name
database_name
Glyn Astill [EMAIL PROTECTED] writes:
I've setup a warm standby reading WAL files, however when I try to
shut it down I get the message server does not shut down.
[EMAIL PROTECTED]:/mnt/archive$ /usr/local/pgsql/bin/pg_ctl stop -D
/data/postgres/ -m smart
waiting for server to shut
On Jan 2, 2008 9:04 AM, Mark Steben [EMAIL PROTECTED] wrote:
Postgres admin team,
We are upgrading from Postgres 7.4.5 to 8.2.5 in mid January. We are also
adding new disks
As we go. I am investigating using the new tablespace facility to move our
biggest and most accessed
I think my
=?ISO-8859-13?Q?Ignas_=D0altis?= [EMAIL PROTECTED] writes:
How can I make dump without blobs?
Per the manual:
-b
--blobs
Include large objects in the dump. This is the default behavior except
when --schema, --table, or --schema-only is specified, so the -b switch
is only useful to add large
On Jan 2, 2008 10:40 AM, Chris Hoover [EMAIL PROTECTED] wrote:
Is there a limit to the number of partitions a table can have in PostgreSQL?
The reason I as is we are looking again at partitioning our databases with
the possibility of doing the partitioning by year, month, or even day.
Aha.. excellent, thanks Tom!
Sorry, I shall try to RTFM in the future.
--- Tom Lane [EMAIL PROTECTED] wrote:
Glyn Astill [EMAIL PROTECTED] writes:
I've setup a warm standby reading WAL files, however when I try
to
shut it down I get the message server does not shut down.
[EMAIL
Hi all,
I'm planning a lot of changes for migrating to PostgreSQL 8.3, among
them being a better way of separating data and logs (transaction logs,
that is).
Currently, the OS and log data are on one disk system, and the data
(including configs) are on the other disk system. After creating the
Peter Koczan [EMAIL PROTECTED] writes:
I'm planning a lot of changes for migrating to PostgreSQL 8.3, among
them being a better way of separating data and logs (transaction logs,
that is).
Currently, the OS and log data are on one disk system, and the data
(including configs) are on the
Tom Lane wrote:
Hmmm ... but it sure looks like the values are offset a few fields from
where they belong ... [ meditates awhile... ] Ah, I've sussed it: the
pg_controldata output you showed can be explained exactly by the
assumption that this copy of pg_controldata thinks time_t is 64 bits
Sattler, Thomas (IT) wrote:
Cache, cache, cache, cache.
and consider dropping all indices until after the load is completed..
Thomas Sattler
Morgan Stanley | Technology
750 Seventh Avenue, 14th Floor | New York, NY 10019
Phone: +1 212 762-1212
[EMAIL PROTECTED]
-Original
[EMAIL PROTECTED] (Tom Lane) writes:
Peter Koczan [EMAIL PROTECTED] writes:
I'm planning a lot of changes for migrating to PostgreSQL 8.3, among
them being a better way of separating data and logs (transaction logs,
that is).
Currently, the OS and log data are on one disk system, and the
Bernhard D Rohrer wrote:
Tom Lane wrote:
exactly - I am currently installing a 32bit dapper on a VM in order to
do the migration
thanks muchly :)
Bernhard
ok, done. worked like a charm. thanks!
Bernhard
--
Graylion's Fetish Fashion Store
Goth and Kinky Boots, Clothing and Jewellery
how do u know this theory ? 1 + (2 * number of columns in the SELECT)
just try test? or have any document?
Guillaume Lelarge-3 wrote:
Tom Lane wrote:
ivan.hou [EMAIL PROTECTED] writes:
step 1. SELECT datname, age(datfrozenxid) FROM pg_database;
-- mydb age:33183
step 2. SELECT datname,
Hello all,
I am trying to build PG 8.3Beta4 for MacOS Leopard.
It works fine when using the default i386 architecture. However, this
is not an option as Apple, in their wisdom, have chosen to build
Apache as a 64-bit application and their PHP 5.2.4 module without PG
support as a Intel 32,
Chris Ruprecht [EMAIL PROTECTED] writes:
I am trying to build PG 8.3Beta4 for MacOS Leopard.
It works fine when using the default i386 architecture. However, this
is not an option as Apple, in their wisdom, have chosen to build
Apache as a 64-bit application and their PHP 5.2.4 module
Chris Ruprecht wrote:
Hello all,
I am trying to build PG 8.3Beta4 for MacOS Leopard.
It works fine when using the default i386 architecture. However, this is
not an option as Apple, in their wisdom, have chosen to build Apache as
a 64-bit application and their PHP 5.2.4 module without PG
Hi All,
I am using the postgresql 8.2.4 (windows).When I don't have enough space
left on my harddisk, postgresql is logging the message could not write
to log file: No space left on device to Windows event viewer. This
message is written to event viewer a lot of times in a minute.
1) Can
ivan.hou wrote:
how do u know this theory ? 1 + (2 * number of columns in the SELECT)
just try test?
I did this at first, yes. I changed log_statement to all, reload the
configuration, and voila. I've seen that pgAdmin's query tool executes
this number of queries to display the result.
or
25 matches
Mail list logo
