Just to to finish this thread:
We had a corrupted memory bank in the development server, and that
was, for some reason corrupting the data that got written to disk.
All is good now. Sorry for the noise.
El día 23 de marzo de 2011 16:28, Martín Marqués
escribió:
> 2011/3/23 Vick Khera :
>> 2011/
2011/3/23 Vick Khera :
> 2011/3/23 Martín Marqués :
>> The second error is very curious, as it looks like pg_dump changed 1
>> for a 'q' in an integer field:
>>
>> psql:siprebi-bu.sql:2219245: ERROR: la sintaxis de entrada no es
>> válida para integer: «q721695»
>> CONTEXT: COPY objeto_datos_rep,
On 03/23/2011 10:33 AM, Martín Marqués wrote:
El día 23 de marzo de 2011 14:03, Adrian Klaver
escribió:
On 03/23/2011 07:56 AM, Martín Marqués wrote:
Ok, did a remote dump (from the development server which has pg 8.4)
and I got a similar error:
psql:siprebi-bu.sql:27374: ERROR: sintaxis
2011/3/23 Martín Marqués :
> The second error is very curious, as it looks like pg_dump changed 1
> for a 'q' in an integer field:
>
> psql:siprebi-bu.sql:2219245: ERROR: la sintaxis de entrada no es
> válida para integer: «q721695»
> CONTEXT: COPY objeto_datos_rep, línea 991894, columna codigo:
El día 23 de marzo de 2011 14:03, Adrian Klaver
escribió:
> On 03/23/2011 07:56 AM, Martín Marqués wrote:
>>
>>
>> Ok, did a remote dump (from the development server which has pg 8.4)
>> and I got a similar error:
>>
>> psql:siprebi-bu.sql:27374: ERROR: sintaxis de entrada no
>> vlida para tipo b
On 03/23/2011 07:56 AM, Martín Marqués wrote:
El día 23 de marzo de 2011 11:18, Adrian Klaver
escribió:
On Wednesday, March 23, 2011 6:57:35 am Martín Marqués wrote:
Now I'm getting weirder things. I did a pg_dump with -d option and the
dump adds strange caracters:
As previously stated
El día 23 de marzo de 2011 11:18, Adrian Klaver
escribió:
> On Wednesday, March 23, 2011 6:57:35 am Martín Marqués wrote:
>
>> Now I'm getting weirder things. I did a pg_dump with -d option and the
>
>> dump adds strange caracters:
>
> As previously stated try using the 8.4 version of pg_dump to d
On Wednesday, March 23, 2011 6:57:35 am Martín Marqués wrote:
> Now I'm getting weirder things. I did a pg_dump with -d option and the
> dump adds strange caracters:
As previously stated try using the 8.4 version of pg_dump to dump the 8.3
database. FYI in 8.4+ there is no -d option anymore, it h
Now I'm getting weirder things. I did a pg_dump with -d option and the
dump adds strange caracters:
ERROR: error de sintaxis en o cerca de «I»
LÍNEA 1: I^NSERT INTO objeto_datos_rep VALUES (1172339, 387943, 'Wilde...
Could it be binary corruption (pg_dump for example)?
2011/3/23 Vick Khera :
>
2011/3/23 Martín Marqués :
> The scenario is like this. I tried today to dump a DB from our
> production server to load on our development server and got some
> errors, which I show below.
Try using the pg_dump from the 8.4 install to create your dump file.
Also make sure your 8.3 installation d
Hi all,
I'm having problems with pg_dump, apparently, from one of our servers.
The scenario is like this. I tried today to dump a DB from our
production server to load on our development server and got some
errors, which I show below.
Production server:
SELECT version();
Im using Red Hat Enterprise Linux 4. Thing is it worked before christmas but
doesn't now. I've just moved the data across by hand so its not too much of
a problem anymore. Might need to use dump again though so would be nice to
get the problem fixed
Tom Lane-2 wrote:
>
> JTyrrell <[EMAIL PROT
JTyrrell <[EMAIL PROTECTED]> writes:
> 1. pg_dump -s doesn't work. I've tried using a load of other options and
> none at all but no luck.
> 2. I'm running as root so wont be a problem there, and the file im dumping
> to has full permissions for everyone.
> What makes this even more confusing i
Richard Huxton wrote:
>
> JTyrrell wrote:
>>
>> pg_dump -a -d testrig > testrig.data
>>
>> on a machine running postgresql 7.4.13 with database testirg i have no
>> problem.
>>
>> Then, I want to do the same but on a different machine running postgresql
>> 7.4.6 with database root. So...
>>
JTyrrell wrote:
pg_dump -a -d testrig > testrig.data
on a machine running postgresql 7.4.13 with database testirg i have no
problem.
Then, I want to do the same but on a different machine running postgresql
7.4.6 with database root. So...
pg_dump -a -d root > root.data
For some reason this d
Hi everyone,
I'm having problems using pg_dump.
When I run the command
pg_dump -a -d testrig > testrig.data
on a machine running postgresql 7.4.13 with database testirg i have no
problem.
Then, I want to do the same but on a different machine running postgresql
7.4.6 with database root. So.
am 09.12.2005, um 12:21:25 +0100 mailte [EMAIL PROTECTED] folgendes:
> Hi !
>
> We have an old web service with a pgsql database (in Suse Linux). This
> database created by another programmer who no accessible now.
>
> We want to dump this database to get data from it. But I have no passwords.
Hi !
We have an old web service with a pgsql database (in Suse Linux). This
database created by another programmer who no accessible now.
We want to dump this database to get data from it. But I have no passwords.
I do many things, but I cannot create dump from this database.
I know the name
18 matches
Mail list logo
