Same version of DB for dump & restore? If not, was the dump done via the
pg_dump from the newer version. If not, please do that.
--
Dan Langille
http://langille.org/
On Aug 28, 2013, at 2:56 AM, Torello Querci wrote:
> Interesting .
>
> while trying to restore the database on the same
2013/8/28 Luca Ferrari
> On Wed, Aug 28, 2013 at 1:08 PM, Torello Querci wrote:
> > Again, is very strange that this data is in the database moreover
> this
> > data came from a import procedure and this data is not present in the
> source
> > import file.
> > Really, I think that I get som
On Wed, Aug 28, 2013 at 1:08 PM, Torello Querci wrote:
> Again, is very strange that this data is in the database moreover this
> data came from a import procedure and this data is not present in the source
> import file.
> Really, I think that I get some kind of data corruption
I'm sure yo
2013/8/28 Dan Langille
> Same version of DB for dump & restore? If not, was the dump done via the
> pg_dump from the newer version. If not, please do that.
>
>
I'm using the same version. I make this test on the same machine.
Moreover I try to remove this line using pgadmin and I get the same err
Interesting .
while trying to restore the database on the same machine as different
database I get this error message:
ERROR: date/time field value out of range: "20016009:50:37.927936"
Since I get this data from a database dump obtained with "pg_dump" on the
same hardware I suppose that ca
2013/8/26 Jeff Janes
> On Mon, Aug 26, 2013 at 10:01 AM, Torello Querci
> wrote:
> > Ok,
> >
> > now create index is finished using maintenance_work_mem=100MB.
> >
> > Thanks to all.
> >
> > I suppose that an error message more clear can help.
>
> Unfortunately, since no one knows what the real
Yes,
the table is bigger than 512MB.
Thank got your tips.
Best Regard, Torello
2013/8/26 Rafael Martinez Guerrero
> On 08/26/2013 06:37 PM, Torello Querci wrote:
> >
> >
> > In this moment I get this error while executing the restore of the big
> > table in a different database on the same m
On Mon, Aug 26, 2013 at 10:01 AM, Torello Querci wrote:
> Ok,
>
> now create index is finished using maintenance_work_mem=100MB.
>
> Thanks to all.
>
> I suppose that an error message more clear can help.
Unfortunately, since no one knows what the real problem is, we can't
make the message more c
On 08/26/2013 06:37 PM, Torello Querci wrote:
>
>
> In this moment I get this error while executing the restore of the big
> table in a different database on the same machine:
>
> psql:dump_ess_2013_08_26.sql:271177424: SSL error: sslv3 alert
> unexpected message
> psql:dump_ess_2013_08_26.sql:2
Ok,
now create index is finished using maintenance_work_mem=100MB.
Thanks to all.
I suppose that an error message more clear can help.
Best Regards, Torello
2013/8/26 Torello Querci
>
>
>
> 2013/8/26 Tom Lane
>
>> Torello Querci writes:
>> > 2013/8/26 Luca Ferrari
>> >> Is it possible t
2013/8/26 Tom Lane
> Torello Querci writes:
> > 2013/8/26 Luca Ferrari
> >> Is it possible to test with an incremented work_mem value?
>
> > Actually I use the default work_set value (1MB).
>
> maintenance_work_mem is what would be used for CREATE INDEX.
>
> Ok thanks
> FWIW, though, the
Torello Querci escribió:
> 2013/8/26 Luca Ferrari
>
> > On Mon, Aug 26, 2013 at 4:27 PM, Torello Querci wrote:
> > > ERROR: unexpected end of tape
> >
> > Really strange, if I get it right something went wrong while sorting
> > tuples.
> > Is it possible to test with an incremented work_mem val
Torello Querci writes:
> 2013/8/26 Luca Ferrari
>> Is it possible to test with an incremented work_mem value?
> Actually I use the default work_set value (1MB).
maintenance_work_mem is what would be used for CREATE INDEX.
FWIW, though, the combination of this weird error and the fact that you
2013/8/26 Luca Ferrari
> On Mon, Aug 26, 2013 at 4:27 PM, Torello Querci wrote:
> > ERROR: unexpected end of tape
>
> Really strange, if I get it right something went wrong while sorting
> tuples.
> Is it possible to test with an incremented work_mem value?
>
> Actually I use the default work_s
2013/8/26 Florian Weimer
> On 08/26/2013 04:27 PM, Torello Querci wrote:
>
>> Create index statement that I use is:
>>
>> CREATE INDEX dati_impianto_id_tipo_dato_id_**data_misurazione_idx
>>ON dati
>>USING btree
>>(impianto_id , tipo_dato_id , data_misurazione DESC);
>>
>
> What are
On Mon, Aug 26, 2013 at 4:27 PM, Torello Querci wrote:
> ERROR: unexpected end of tape
Really strange, if I get it right something went wrong while sorting tuples.
Is it possible to test with an incremented work_mem value?
Luca
--
Sent via pgsql-general mailing list (pgsql-general@postgresql
On 08/26/2013 04:27 PM, Torello Querci wrote:
Create index statement that I use is:
CREATE INDEX dati_impianto_id_tipo_dato_id_data_misurazione_idx
ON dati
USING btree
(impianto_id , tipo_dato_id , data_misurazione DESC);
What are the data types of these columns?
--
Florian Weimer /
Hi to all
On my Postgresql 9.1 instance I had a problem with an index.
Using index I get less tuples than expected.
I try to remove index and the query works fine but obviosly the query is
slow so I try to recreate the index.
I run the create index statement but after a lot of time I get thi
18 matches
Mail list logo
