Marco Bizzarri schrieb:
Hi all.
Here is my use case: I've an application which uses PostgreSQL as
backend. Up to now, the database was encoded in SQL_ASCII or LATIN1.
Now, we need to migrate to UTF-8.
What we tried, was to:
1) dump the database using pg_dump, in tar format (we had blob);
2)
On 7/6/06, Tino Wildenhain [EMAIL PROTECTED] wrote:
Marco Bizzarri schrieb:
Hi all.
Here is my use case: I've an application which uses PostgreSQL as
backend. Up to now, the database was encoded in SQL_ASCII or LATIN1.
Now, we need to migrate to UTF-8.
What we tried, was to:
1) dump the
...
Yes, its actually quite esay: you dump as you feel apropriate,
then create the database with the encoding you want,
restore w/o creating database and you are done.
Restore sets the client encoding to what it actually was
in the dump data (in your case latin-1) and the database
would be utf-8
On 7/6/06, Tino Wildenhain [EMAIL PROTECTED] wrote:
...
Yes, its actually quite esay: you dump as you feel apropriate,
then create the database with the encoding you want,
restore w/o creating database and you are done.
Restore sets the client encoding to what it actually was
in the dump
Jasbinder Bali wrote:
Hi
Can anyone help me with the usage of ECPG??
Like how to go about it, what all header files to include in my C file
and other things that i need to give due considerations before using ECPG
~Jas
see headOfPgSourceTree/src/interfaces/ecpg ( test has several examples )
Hi,
Anyone knows a good tool for do the reverse engineering
of a postgresql database? I tried to use DBDesigner, but I couldnt get the
relationships!
Thanks!
On 7/6/06, Rodrigo Sakai [EMAIL PROTECTED] wrote:
Anyone knows a good tool for do the reverse engineering of a postgresql
database? I tried to use DBDesigner, but I couldn't get the relationships!
I would suggest pgadmin, or the very excellent ems administrator (pro
version). EMS
Dear friends,
in postgresql 8.0.7 I have the following table
\d
basedati
Colonna |Tipo |
Modificatori
--+-+--
data_ora | timestamp without time zone |
cod_wmo | character
(5)|
t_aria
Hi
I've implemented replication to a warm standby using wal
logshipping now. The only remaining problem is that there
is no way in 8.1 to force postgres to close the current
wal segment, and start using a new one.
Therefor, if there is little traffic, changes can take
a long time to actually
Michael Fuhr wrote:
On Wed, Jul 05, 2006 at 02:27:19PM -0700, Karen Hill wrote:
I would like for one role to be able to login, and execute a couple of
functions and nothing else. I've tried to revoke access to CREATE on
the database, schema, and tablespace but when I tested it, the user
On 6 Jul 2006 09:46:48 -0700
Karen Hill [EMAIL PROTECTED] wrote:
Michael Fuhr wrote:
On Wed, Jul 05, 2006 at 02:27:19PM -0700, Karen Hill wrote:
I would like for one role to be able to login, and execute a
couple of functions and nothing else. I've tried to revoke
access to CREATE
On 7/6/06, Florian G. Pflug [EMAIL PROTECTED] wrote:
Hi
I've implemented replication to a warm standby using wal
logshipping now. The only remaining problem is that there
just how exactly does this work? are you constantly firing up the
standby server?
merlin
might also be interested in psql's -q option (or \set QUIET).
I use -q but I've got e.g
Z:\psql.exe -q -d ff -h localhost -p 5432 -U postgres
0D:\ff\centralny\src\db\processing_utils.sql
NOTICE: type reference ff.alias.mask%TYPE converted to character
varying
NOTICE: type reference
I have function (below) that returns values in table format. But when
source table ( xxx.logic_list_item ) is empty I've got following
message in log:
row number -1 is out of range 0..-1
Is it a error message ? To be honest I do not know how to handle
situation when source table is empty, what
This is no small task.
But that a mans reach should exceed his grasp...
All of that being said, if you want to do it yourself, I would still
claim that you'd get there a lot faster adopting Andromeda, because all
you are really trying to do is embellish what we've already done.
The problem
might also be interested in psql's -q option (or \set QUIET).
I use -q but I've got e.g
Z:\psql.exe -q -d ff -h localhost -p 5432 -U postgres
0D:\ff\centralny\src\db\processing_utils.sql
NOTICE: type reference ff.alias.mask%TYPE converted to character
varying
NOTICE: type reference
* Florian G. Pflug ([EMAIL PROTECTED]) wrote:
I'd like to implement that scheme, but am unsure how
to determine that segment reliably. I noticed that
there is an pg_xlog/archive_status directory, which
contains *.done files for some of the archived wal logs.
Personally, I was just lazy and
Merlin Moncure wrote:
On 7/6/06, Florian G. Pflug [EMAIL PROTECTED] wrote:
Hi
I've implemented replication to a warm standby using wal
logshipping now. The only remaining problem is that there
just how exactly does this work? are you constantly firing up the
standby server?
Postgres on
On Wed, Jul 05, 2006 at 07:48:21AM -0700, Szymic1 wrote:
might also be interested in psql's -q option (or \set QUIET).
I use -q but I've got e.g
Z:\psql.exe -q -d ff -h localhost -p 5432 -U postgres
0D:\ff\centralny\src\db\processing_utils.sql
NOTICE: type reference ff.alias.mask%TYPE
Chris [EMAIL PROTECTED] 07/05/06 7:49 PM
Jim Cser wrote:
[post header corrected, sorry]
I have an application that uses ODBC to access a PostGreSQL 8.0.3
database. To load in text files (comma separated, with column
headers),
I use the SQL statement COPY FROM, which requires me to be a
I seem to have a problem accessing a temp table from a trigger when I
use cascading deletes.
I have 2 tables: a main table and a child table. The child table has a
foreign key reference to the main table that has DELETE CASCADE on.
I have delete triggers on both tables that are run BEFORE
On Wed, Jun 21, 2006 at 06:07:33PM -0700, [EMAIL PROTECTED] wrote:
I don't want to revisit or be redundant... but is there a quick and
dirty and cross-platform system for developing user input forms for
Postgres? Ideally, I am interested in something such that you can give
it (it being
On Thu, 2006-07-06 at 13:28, Jim Cser wrote:
Chris [EMAIL PROTECTED] 07/05/06 7:49 PM
Are you trying from a file or stdin? What error message do you get
when
you try?
As I mentioned above, I am loading CSV files, and yes, I do read
documentation. It all works just fine as a superuser,
On Thu, Jul 06, 2006 at 07:37:17AM -0700, Szymic1 wrote:
I have function (below) that returns values in table format. But when
source table ( xxx.logic_list_item ) is empty I've got following
message in log:
row number -1 is out of range 0..-1
What log? What client are you using -- psql or
Hi,
What is the best pg_dump format for long-term database
archival? That is, what format is most likely to
be able to be restored into a future PostgreSQL
cluster.
Mostly, we're interested in dumps done with
--data-only, and have preferred the
default (-F c) format. But this form is somewhat
Hello.
I have client software that I wrote which uses parameters in function
calls to postgresql. I use quote_literal in postgresql functions.
That means I get data that is quoted when it finally ends up in the
tables which I don't want.
I know that you shouldn't trust data sent from the
The problem isn't permission for copy, it permission to access files.
only the super user can access the file system through pgsql, because
of
security concerns.
copy can be run by anybody. copy from/to a FILE can only be done by
the
super user.
Have you tried queueing up copy from stdin and
On Thu, 2006-07-06 at 15:03, Jim Cser wrote:
The problem isn't permission for copy, it permission to access files.
only the super user can access the file system through pgsql, because
of
security concerns.
copy can be run by anybody. copy from/to a FILE can only be done by
the
super
Alex Turner wrote:
As an aside note, I would consider a 13 disk RAID 5 a high risk
solution. If you loose just two drives of 13 at the same time, your
data is all gone. If you loose one drive, your array goes into degraded
mode and your read and write performance goes to hell, and your
Scott Marlowe [EMAIL PROTECTED] 07/06/06 1:23 PM
On Thu, 2006-07-06 at 15:03, Jim Cser wrote:
The problem isn't permission for copy, it permission to access
files.
only the super user can access the file system through pgsql,
because
of
security concerns.
copy can be run by anybody.
On 5 Jul 2006 06:33:34 -0700, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Yesterday I had the big honor to talk (by email) with Shachar and it
seems that they (someday) will fix this fundamental issue.
I tried to stress how important is to support the OleDbSchemaGuid info,
as the main reason
On Thu, Jul 06, 2006 at 08:27:53AM +, Sergey Konoplev wrote:
The following bug has been logged online:
Description:Trouble with cx_Oracle and Plpython
CREATE OR REPLACE FUNCTION public.function1 () RETURNS varchar AS
$body$
import cx_Oracle
connection =
Hi all!
This was 8.1.3 and now is 8.1.4 running on Debian Sarge, locally
compiled without any fancy options.
Since Tuesday we experience strange diconnects from our database
used as a source code respository for the developers.
First indicators of trouble are log lines like
:ERROR: invalid
On Thu, 2006-07-06 at 16:36, Weerts, Jan wrote:
Hi all!
This was 8.1.3 and now is 8.1.4 running on Debian Sarge, locally
compiled without any fancy options.
While the first answer seems much more valid (the primarkey is
an artificially created number), the second answer seems to
be the
Scott Marlowe wrote:
On Thu, 2006-07-06 at 16:36, Weerts, Jan wrote:
Hi all!
This was 8.1.3 and now is 8.1.4 running on Debian Sarge, locally
compiled without any fancy options.
While the first answer seems much more valid (the primarkey is
an artificially created number), the second
Karl O. Pinc wrote:
Hi,
What is the best pg_dump format for long-term database
archival? That is, what format is most likely to
be able to be restored into a future PostgreSQL
cluster.
Mostly, we're interested in dumps done with
--data-only, and have preferred the
default (-F c) format. But
Karen Hill wrote:
Hello.
I have client software that I wrote which uses parameters in function
calls to postgresql. I use quote_literal in postgresql functions.
That means I get data that is quoted when it finally ends up in the
tables which I don't want.
I know that you shouldn't trust
DEBUG: 0: StartTransactionCommand
LOCATION: start_xact_command, postgres.c:1981
DEBUG: 0: ProcessQuery
LOCATION: ProcessQuery, pquery.c:128
STATEMENT: INSERT INTO links VALUES ($1, $2, $3)
PANIC: XX000: right sibling is not next child in
pg_depend_reference_index
LOCATION:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florian G. Pflug wrote:
Karl O. Pinc wrote:
[snip]
Anyway, 20 years is a _long_, _long_ time. If you _really_ need
to keep your data that long, I'd suggest you create text-only
schema dumps, and text-only data dumps. The postgres developers
are
Will postgresql be a viable database in 20 years? Will SQL be used
anywhere in 20 years? Are you sure 20 years is your ideal backup
duration?
Very few media even last 5 years. The good thing about open source and
open standards is that regardless of the answers to those questions,
there is
On 07/06/2006 06:14:39 PM, Florian G. Pflug wrote:
Karl O. Pinc wrote:
Hi,
What is the best pg_dump format for long-term database
archival? That is, what format is most likely to
be able to be restored into a future PostgreSQL
cluster.
Anyway, 20 years is a _long_, _long_ time.
Yes, but
Will postgresql be a viable database in 20 years? Will SQL be used
anywhere in 20 years? Are you sure 20 years is your ideal backup
duration?
Very few media even last 5 years. The good thing about open source and
open standards is that regardless of the answers to those questions,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Agent M wrote:
Will postgresql be a viable database in 20 years? Will SQL be used
anywhere in 20 years? Are you sure 20 years is your ideal backup duration?
SQL was used 20 years ago, why not 20 years from now?
I can't see needing data from 10
I am not to sure of the relevance, but I periodically worked as a
sub-contractor for an
Oil-producing Company in California. They were carrying 35 years of
data on an Alpha Server
running Ca-Ingres. The really bad part is that hundreds and hundreds
of reporting tables were
created on top of
On Thu, Jul 06, 2006 at 09:55:40AM -0700, John Purser wrote:
Karen Hill [EMAIL PROTECTED] wrote:
Revoking PUBLIC worked. I can now login to the database and it will
not allow me to create new tables. However when I gave (as postgres)
the restricted user permission to execute one function
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Richard Broersma Jr wrote:
[snip]
I am not to sure of the relevance, but I periodically worked as a
sub-contractor for an Oil-producing Company in California. They
were carrying 35 years of data on an Alpha Server running
Ca-Ingres. The
But the data from 35 years ago wasn't stored in Ingres and, if it's
important, it won't stay in Ingres. The data shifts from format to
format as technology progresses.
It seemed to me that the OP wanted some format that would be readable
in 20 years. No one can guarantee anything like
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Agent M wrote:
[snip]
But the data from 35 years ago wasn't stored in Ingres and, if
it's important, it won't stay in Ingres. The data shifts from
format to format as technology progresses.
Ingres has been around for longer than you think: about
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-general-
[EMAIL PROTECTED] On Behalf Of Ron Johnson
Sent: Thursday, July 06, 2006 5:26 PM
To: Postgres general mailing list
Subject: Re: [GENERAL] Long term database archival
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jul 06, 2006 at 02:06:46PM -0400, Brennan, Sean (IMS) wrote:
All in the same db connection, I do the following:
1)create a temp table
2)delete rows from the main table
3)access the temp table in the delete trigger of the main table
4)access the temp table in the delete trigger of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dann Corbit wrote:
-Original Message-
From: [EMAIL PROTECTED] [mailto:pgsql-general-
[EMAIL PROTECTED] On Behalf Of Ron Johnson
Sent: Thursday, July 06, 2006 5:26 PM
To: Postgres general mailing list
Subject: Re: [GENERAL] Long term
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Being an HP/Compaq shop, I'm looking at an Opteron-and-SATA-based
DL145 G2 and an MSA20 SATA enclosure with a U320 interface to use
with RHES4 and PostgreSQL.
Anyone have Experience with this h/w+s/w combo? It will be used as
a history server, so
On Thursday 06 July 2006 19:55, Ron Johnson wrote:
Being an HP/Compaq shop, I'm looking at an Opteron-and-SATA-based
DL145 G2 and an MSA20 SATA enclosure with a U320 interface to use
with RHES4 and PostgreSQL.
I recently speced this exact hardware for a customer. When the customer called
HP to
Ryan Gran [EMAIL PROTECTED] writes:
PANIC: XX000: right sibling is not next child in
pg_depend_reference_index
Perhaps this is explained here?
http://archives.postgresql.org/pgsql-general/2006-04/msg00848.php
Using 8.1.0 under OS/X.
You are of course aware that we are up to 8.1.4, and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joshua D. Drake wrote:
On Thursday 06 July 2006 19:55, Ron Johnson wrote:
Being an HP/Compaq shop, I'm looking at an Opteron-and-SATA-based
DL145 G2 and an MSA20 SATA enclosure with a U320 interface to use
with RHES4 and PostgreSQL.
I recently
OK I know this is an odd question but I'm working on an app that will rely
more and more on database driven functions, and while the app's source is
in SVN, and I intend for the source of the SQL scripts to also be there, I
was wondering...what are people doing for version control and change
56 matches
Mail list logo
