Hello,
I try to restore a dump file on a new Database. But unfortunatly i get this
error:
pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 532; 2612 16386 PROCEDURAL
LANGUAGE plpgsql postgres
pg_restore: [archiver (db)] could not
I found comment in src/backend/optimizer/path/pathkeys.c:
* EXCEPTION: in a FULL or RIGHT join, we cannot treat the result as
* having the outer path's path keys, because null lefthand rows may be
* inserted at random points. It must be treated as unsorted.
How can I get rid of this
Maciej Sieczka wrote:
I need to modify this default PostgreSQL's behaviour, so that the ACL on
a new table in this schema is set to SELECT, INSERT, UPDATE, DELETE,
REFERENCES for editors, and SELECT for viewers, without having to
manually GRANT rights each time a new table is created. I can't
On Mon, Feb 25, 2008 at 06:40:43PM +0100, Andreas Lau wrote:
Hello,
I try to restore a dump file on a new Database. But unfortunatly i get this
error:
pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 532; 2612 16386 PROCEDURAL
On Tue, Feb 26, 2008 at 10:26:25AM +0100, Martijn van Oosterhout wrote:
On Tue, Feb 26, 2008 at 10:23:05AM +0100, Magnus Hagander wrote:
Any chance you are running pg_dump/pg_restore version 8.3? The syntax
appears to be what 8.3 uses, not 8.3..
You can use (and should use) an 8.3
On Tue, Feb 26, 2008 at 10:23:05AM +0100, Magnus Hagander wrote:
Any chance you are running pg_dump/pg_restore version 8.3? The syntax
appears to be what 8.3 uses, not 8.3..
You can use (and should use) an 8.3 pg_dump to dump your 8.2 database when
upgrading to 8.3, but you often can't
ERROR: canceling autovacuum task
CONTEXT: automatic vacuum of table metadb.test.transactions
Are these happening regularly? They indicate that something is
happening on the table that collides with what autovacuum needs to do,
and autovacuum defers its task. For this to happen you need to
Thanks for your hinds.
It's true i used pg_dump and pg_restore version 8.3 to dump and restore 8.2
databases. I wouldn't have thought that there could be problems. But it seems
so. I will give it a try an report the result.
Thanks Andreas
-Ursprüngliche Nachricht-
Von: Magnus Hagander
Alexey A. Nalbat [EMAIL PROTECTED] writes:
Yes. But may be the FULL MERGE JOIN could be improved, because it
is ordered, it actually has outer path's path key: coalesce(id1,id2).
Hm, there's more going on here than meets the eye. If you changed the query
slightly Postgres would actually
On Tue, Feb 26, 2008 at 3:11 PM, Stuart Brooks [EMAIL PROTECTED] wrote:
ERROR: canceling autovacuum task
CONTEXT: automatic vacuum of table metadb.test.transactions
Are these happening regularly? They indicate that something is
happening on the table that collides with what
ERROR: canceling autovacuum task
CONTEXT: automatic vacuum of table metadb.test.transactions
Are these happening regularly? They indicate that something is
happening on the table that collides with what autovacuum needs to do,
and autovacuum defers its task. For this to happen
I'm working on a CMS that, in addition to the database-stored version
of articles for easy searching, sorting, etc, also stores a HTML file
version so pages can be fetched with the minimum of overhead (browsing
articles has no more overhead than accessing any other HTML file on
the server).
As
Gordon wrote:
I need to find a way of not running queries that I don't need to,
either in the PHP script, or in the Postgres database. What I need is
for a result set to be cached somewhere, either by Postgres or PHP, so
when it sees the same query again in a given session it just returns
the
Stuart Brooks [EMAIL PROTECTED] writes:
It'll take a few minutes but I'll try and get the information to you. A
summary
is:
Process 1:
- writing 50 rows/second, 1 row/transaction.
- every so often delete 100 rows
Process 2:
- running ANALYZE VERBOSE and pg_total_relation_size every
Stuart Brooks wrote:
I am not using an ALTER table command but I am doing periodic ANALYZEs
to evaluate the table size. Could this be causing the problem? I notice
that stopping the ANALYZE calls appears to eliminate the canceled
autovacuum.
Why were you running ANALYZE on the first
My problem seems to be solved. Actually it was because of the differences
between the version of pg_dump/pg_restore (8.3) and of my postgres DB (8.2.6).
As i used the appropriate versions for pg_dump/pg_restore the restauration runs
through without any errors.
Thanks for that Andreas
Actually
It'll take a few minutes but I'll try and get the information to you. A summary
is:
Process 1:
- writing 50 rows/second, 1 row/transaction.
- every so often delete 100 rows
Process 2:
- running ANALYZE VERBOSE and pg_total_relation_size every second
You'll probably have to vacuum
Il giorno 24/feb/08, alle ore 04:53, justin tocci ha scritto:
In its most basic form a great tool would just start as a pl/pgsql
or pl/perl function that could be used to call a table and have it
output a batch of records to an editable html form or a colored pdf
for nice reports. There
--- justin tocci [EMAIL PROTECTED] wrote:
interface? I've thought about it enough to want to try it. I don't
really know how APEX / HTML DB work so I'm open to suggestions. I
can
either put the controller in a perl module and send intelligent
requests for formatted pages to postgres or
What concerns me is that once the size has grown, even a VACUUM FULL
doesn't recover the space. Regular external VACUUMs keep the table at
around 10MB but if I use autovacuum and it grows to 40MB, a VACUUM FULL
will only get it down to 35MB. Is it possible that a canceled autovacuum
could
I have the following problem getting to connect a remote database (MS
SQL Server in my case) to PostgreSQL.
I'm using SQL Server 2005 Express Edition. I tried it with the following:
SELECT dbi_link.make_accessor_functions(
'dbi:ODBC:DRIVER=SQL Native
Gregory Stark [EMAIL PROTECTED] writes:
Alexey A. Nalbat [EMAIL PROTECTED] writes:
Yes. But may be the FULL MERGE JOIN could be improved, because it
is ordered, it actually has outer path's path key: coalesce(id1,id2).
No, it does not have the outer path's path key. The outer path's key
is
On Tue, 2008-02-26 at 10:34 -0500, Tom Lane wrote:
and add COALESCE(id2,id1) to it as well I think.
No, because those two expressions are not equivalent. (Hmm ... squint
... but full merge join is pretty much symmetric, so it's not clear
why it should matter which side is left or right.
Richard Huxton pisze:
Maciej Sieczka wrote:
I need to modify this default PostgreSQL's behaviour, so that the ACL on
a new table in this schema is set to SELECT, INSERT, UPDATE, DELETE,
REFERENCES for editors, and SELECT for viewers, without having to
manually GRANT rights each time a new
Stuart Brooks [EMAIL PROTECTED] writes:
Process 2:
- running ANALYZE VERBOSE and pg_total_relation_size every second
The result is that autovacuum appears to be canceled.
Yes, that will pretty much guarantee that an autovacuum is never able to
complete...
What concerns me is that once the
Simon Riggs [EMAIL PROTECTED] writes:
On Tue, 2008-02-26 at 10:34 -0500, Tom Lane wrote:
and add COALESCE(id2,id1) to it as well I think.
No, because those two expressions are not equivalent. (Hmm ... squint
... but full merge join is pretty much symmetric, so it's not clear
why it should
Stuart Brooks wrote:
It'll take a few minutes but I'll try and get the information to you. A
summary is:
Process 1:
- writing 50 rows/second, 1 row/transaction.
- every so often delete 100 rows
Process 2:
- running ANALYZE VERBOSE and pg_total_relation_size every second
The result is that
Hi,
How can I make custom conversion? The postgres-documentation can't help
me :(
I'm find this only, but without any examples:
http://www.postgresql.org/docs/8.3/interactive/sql-createconversion.html
CREATE [ DEFAULT ] CONVERSION name
FOR source_encoding TO dest_encoding FROM
On Feb 26, 11:11 am, Gordon [EMAIL PROTECTED] wrote:
I'm working on a CMS that, in addition to the database-stored version
of articles for easy searching, sorting, etc, also stores a HTML file
version so pages can be fetched with the minimum of overhead (browsing
articles has no more overhead
Gordon wrote:
I'm working on a CMS that, in addition to the database-stored version
of articles for easy searching, sorting, etc, also stores a HTML file
version so pages can be fetched with the minimum of overhead (browsing
articles has no more overhead than accessing any other HTML file on
the
Maciej Sieczka wrote:
Richard Huxton pisze:
Afraid not. You can't add a trigger to a system table.
Too bad, but thanks much for clarifying this.
The only real solution is to have your own function do both - create
the table and then grant relevant permissions. Only allow client
I wrote:
Gregory Stark [EMAIL PROTECTED] writes:
as a path key, though we would have to create an equivalence class
and add COALESCE(id2,id1) to it as well I think.
No, because those two expressions are not equivalent. (Hmm ... squint
... but full merge join is pretty much symmetric, so
Norman Peelman [EMAIL PROTECTED] writes:
My options are, as far as I can tell,
1) replace the Database PDO extending class with something else that
provides query results caching in PHP, or
2) get Postgres itself to cache the results of queries to avoid
running them repeatedly during a
TJ O'Donnell wrote:
I've been running PostgreSQL on a virtual server for several years
now. I'm using VMWare with a Windows host and Linux guest. I've
configured it to let Linux use a raw partition as a disk. Before I
used a separate partition, the virtual disk had been a Windows
file. Using
Tom Lane [EMAIL PROTECTED] writes:
I wrote:
Gregory Stark [EMAIL PROTECTED] writes:
as a path key, though we would have to create an equivalence class
and add COALESCE(id2,id1) to it as well I think.
No, because those two expressions are not equivalent. (Hmm ... squint
... but full merge
Yuri Gordienko [EMAIL PROTECTED] writes:
How can I make custom conversion? The postgres-documentation can't help
me :(
I'd suggest you start by copying-and-pasting one of the existing
conversion functions. Look under src/backend/utils/mb/conversion_procs/
in the source distribution.
Gregory Stark [EMAIL PROTECTED] writes:
Tom Lane [EMAIL PROTECTED] writes:
It might still be interesting sometime to have a more bespoke
representation for a merged variable, but I guess we don't need
it just for this.
It might have an advantage if you're doing a three-way outer join and
Richard Huxton pisze:
Maciej Sieczka wrote:
Richard Huxton pisze:
Afraid not. You can't add a trigger to a system table.
Too bad, but thanks much for clarifying this.
The only real solution is to have your own function do both - create
the table and then grant relevant permissions. Only
Maciej Sieczka wrote:
I'd like to prevent concurrent editing of a table. For example PostGIS
tables, which are going to be stored in the database too: once a user
starts editing the table in QGIS [1], it should be locked (for writing
at least), until he turns the edit mode off and commits
Hello everybody. I recently converted my db from ASCII encoding to UTF8
(we have a lot of spanish-speaking members, and need the extra character
support). Everything was working great, but I noticed this error, while
trying to COPY one of our tables from a csv.
ERROR: invalid byte sequence
Is there a simple way to copy a table from one database to another without
generating an intermediate dump file?
TIA!
Kynn
Kynn Jones wrote:
Is there a simple way to copy a table from one database to another
without generating an intermediate dump file?
TIA!
Kynn
You're looking for ETL.
http://en.wikipedia.org/wiki/Extract%2C_transform%2C_load
--
Tom Hart
IT Specialist
Cooperative Federal
723 Westcott St.
On Tue, Feb 26, 2008 at 9:19 PM, Kynn Jones [EMAIL PROTECTED] wrote:
Is there a simple way to copy a table from one database to another without
generating an intermediate dump file?
Using UNIX pipes :-)
$ pg_dump ... | psql ...
:-)
Regards,
Dawid
---(end
Tom Hart wrote:
Hello everybody. I recently converted my db from ASCII encoding to UTF8
(we have a lot of spanish-speaking members, and need the extra character
support). Everything was working great, but I noticed this error, while
trying to COPY one of our tables from a csv.
ERROR: invalid
Kynn Jones wrote:
Is there a simple way to copy a table from one database to another without
generating an intermediate dump file?
Something along the lines of:
pg_dump ... -d db1 --table=mytable | psql -d db2
--
Richard Huxton
Archonet Ltd
---(end of
On Tuesday 26 February 2008, Kynn Jones wrote:
Is there a simple way to copy a table from one database to another without
generating an intermediate dump file?
TIA!
Kynn
pg_dump -t [table] [database] | psql -U [remoteuser] -h [remotehost]
[remotedatabase]
comes to mind...
You can and
On Tue, 2008-02-26 at 15:19 -0500, Kynn Jones wrote:
Is there a simple way to copy a table from one database to another
without generating an intermediate dump file?
pg_dump -t table name source DB | psql -d target DB
--
Brad Nicholson 416-673-4106
Database Administrator, Afilias Canada
On Tue, Feb 26, 2008 at 2:36 PM, Brad Nicholson
[EMAIL PROTECTED] wrote:
On Tue, 2008-02-26 at 15:19 -0500, Kynn Jones wrote:
Is there a simple way to copy a table from one database to another
without generating an intermediate dump file?
pg_dump -t table name source DB | psql -d
Tom Hart wrote:
Hello everybody. I recently converted my db from ASCII encoding to UTF8
(we have a lot of spanish-speaking members, and need the extra character
support). Everything was working great, but I noticed this error, while
trying to COPY one of our tables from a csv.
ERROR:
Richard Huxton wrote:
Tom Hart wrote:
Hello everybody. I recently converted my db from ASCII encoding to
UTF8 (we have a lot of spanish-speaking members, and need the extra
character support). Everything was working great, but I noticed this
error, while trying to COPY one of our tables from
Hi,
I urgently need a way to simply backup the database's data on win32
(e.g. the 'data' directory).
As discussed earlier I can't use dump/dumpall since my data needs
persistent tableoids which, however, are not the same after a restore.
AFAIK stopping the server, zipping data dir, and
AFAIK stopping the server, zipping data dir, and restarting
the server creates a zip file which is not easily portable to
other computers due to some ntfs file system permission problems.
IIRC you have to re-assign owner and change permissions after you copy your
data dir to the new server.
[EMAIL PROTECTED] wrote:
Hi,
I urgently need a way to simply backup the database's data on win32
(e.g. the 'data' directory).
As discussed earlier I can't use dump/dumpall since my data needs
persistent tableoids which, however, are not the same after a restore.
AFAIK stopping the server,
On Tue, Feb 26, 2008 at 3:51 PM, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
As discussed earlier I can't use dump/dumpall since my data needs
persistent tableoids which, however, are not the same after a restore.
What about the workarounds / refactoring tips proposed in previous discussions?
Richard Huxton pisze:
Maciej Sieczka wrote:
In PG experts
opinion, could/should a PostGIS editing software lock table for
writing to prevent concurent editing?
The application should either:
1. Take an advisory lock (see the functions/admin functions chapter) so
that it can use another
On 2008-02-26 13:04, Tom Hart wrote:
I already have a php script that does some data scrubbing before the
copy. I added this line to the script and things seem to be working
better now
$line = iconv(ISO-8859-1, UTF-8, $line);
Thanks for the help guys :-)
Read up on the difference
I just downloaded postgres 8.3 for windows and noticed that citext is
not an option for columns.
The web site has the source code but no binaries for windows.
I downloaded the enterprisedb and noticed that it has the citext.dll
in the lib directory so I copied the dll over to the postgres lib
I'm not sure if you're saying I should ignore these errors...
I'm using dumps from DB airaburst.
postgres=# \l
List of databases
Name| Owner | Encoding
+--+---
airburst | root | SQL_ASCII
lt_dev1| postgres | UTF8
lt_dev2|
Ralph Smith [EMAIL PROTECTED] writes:
I'm not sure if you're saying I should ignore these errors...
No, not at all.
I'm using dumps from DB airaburst.
Doesn't look like that --- you have
Name| Owner | Encoding
+--+---
airburst | root |
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gevik
Babakhani
Sent: Tuesday, 26 February 2008 22:30
To: [EMAIL PROTECTED]; pgsql-general@postgresql.org
Subject: Re: [GENERAL] win32: how to backup (dump does not work)
AFAIK stopping the server,
These create table commands succeed, even tho the foreign key refers to a
'different' type (int2 product_id column refers to an int8 column):
CREATE TABLE products (
id int8 primary key,
name text not null
);
CREATE TABLE orders (
id int8 PRIMARY KEY,
product_id int2 not null
On Tue, 26 Feb 2008, craigp wrote:
These create table commands succeed, even tho the foreign key refers to
a 'different' type (int2 product_id column refers to an int8 column):
The requirements in recent SQL specs appears to be that the column types
are comparable, not the same.
SQL2003 11.8
Hello !
I have a week number (ISO 8601) and a year, based on theses values, I
would like to get the first and the last dates of that week.
How I can do that ?
The only solution is doing a big generate_series to build a subset that
contains the week of all the dates between the 01/01 || year
On Tuesday 26 February 2008 5:32 pm, Bruno Baguette wrote:
Hello !
I have a week number (ISO 8601) and a year, based on theses values, I
would like to get the first and the last dates of that week.
How I can do that ?
The only solution is doing a big generate_series to build a subset that
Bruno Baguette wrote:
Hello !
I have a week number (ISO 8601) and a year, based on theses values, I
would like to get the first and the last dates of that week.
How I can do that ?
The only solution is doing a big generate_series to build a subset that
contains the week of all the dates
Where can I get uuid-ossp for windows? Also where can I get citext for windows.
These two are missing from the windows installer.
Thanks.
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
On Tue, Feb 26, 2008 at 9:44 PM, Tim Uckun [EMAIL PROTECTED] wrote:
Where can I get uuid-ossp for windows? Also where can I get citext for
windows.
These two are missing from the windows installer.
Search the archives. There was a conversation about this in the last
week or two.
Stephan Szabo [EMAIL PROTECTED] writes:
On Tue, 26 Feb 2008, craigp wrote:
These create table commands succeed, even tho the foreign key refers to
a 'different' type (int2 product_id column refers to an int8 column):
The requirements in recent SQL specs appears to be that the column types
Hi.
- Original Message -
From: Scott Marlowe [EMAIL PROTECTED]
On Tue, Feb 26, 2008 at 9:44 PM, Tim Uckun [EMAIL PROTECTED] wrote:
Where can I get uuid-ossp for windows? Also where can I get citext for windows.
These two are missing from the windows installer.
Search the
Adrian Klaver [EMAIL PROTECTED] writes:
On Tuesday 26 February 2008 5:32 pm, Bruno Baguette wrote:
I have a week number (ISO 8601) and a year, based on theses values, I
would like to get the first and the last dates of that week.
This will get you to the Monday of the week .
select
Anyone have any ideas, or is there another list for install questions?
Dee [EMAIL PROTECTED] wrote: I am trying to install version 8.3 on windows
2000. I created a Local account named postgres and granted it Log on as a
service and Log on locally rights as described here
On Tuesday 26 February 2008 8:39 pm, Tom Lane wrote:
Adrian Klaver [EMAIL PROTECTED] writes:
On Tuesday 26 February 2008 5:32 pm, Bruno Baguette wrote:
I have a week number (ISO 8601) and a year, based on theses values, I
would like to get the first and the last dates of that week.
This
Adrian Klaver [EMAIL PROTECTED] writes:
On Tuesday 26 February 2008 8:39 pm, Tom Lane wrote:
date_trunc('week', ...) would probably be a more convenient way of doing
that.
I am not sure I follow. The OP has a ISO week number and a year and wants
dates. I thought date_trunc('field',source)
Richard, did you ever get this issue sorted?
I have encountered a similar situation that came about when I upgraded
to postgres 8.3. Now it won't start stating that:
The server must be started under the locale : which does not exist any more
(it looks like the locale is set to {blank} ???)
Process 2:
- running ANALYZE VERBOSE and pg_total_relation_size every second
The result is that autovacuum appears to be canceled.
Yes, that will pretty much guarantee that an autovacuum is never able to
complete...
That's what I figured. Since I won't be running ANALYZE
75 matches
Mail list logo
