On Dec 19, 2007 1:57 AM, olivier boissard <[EMAIL PROTECTED]> wrote:
> Scott Marlowe a écrit :
>
> > On Dec 18, 2007 4:21 PM, [EMAIL PROTECTED]
> > <[EMAIL PROTECTED]> wrote:
> >
> >> Hello,
> >>
> >> My purpose is to uses different query plan depending on queries
> >> I got the following problem :
I can run the following command from a command prompt with no problem on my
database.
/usr/bin/vacuumdb --verbose --analyze --all -U postgres
But if I try to execute it via a bash shell script, I receive the following
error. The role does exist in the database.
does not existnot connect to d
"Ferry, Craig" <[EMAIL PROTECTED]> writes:
> I can run the following command from a command prompt with no problem on my
> database.
> /usr/bin/vacuumdb --verbose --analyze --all -U postgres
> But if I try to execute it via a bash shell script, I receive the following
> error. The role does ex
You're right .
I will begin by migrate postgresql version.
postgresql is now to 8.3 version . A lot of performance inprovements
have been made in this last version .
In any case I must do a pg_dump/pg_restore.
So , Should I try directly 8.3 version or is it more cautious to stay in
8.1.x versio
Did anybody face the same problem during the compilation of postgresql 8.2.5
on suse 10.2?
I'm using gmake 3.81
gcc -I../../include -I../../../../../src/interfaces/ecpg/include
-I../../../../../src/interfaces/libpq -I../../../../../src/include
-D_GNU_SOURCE -O2
-Wall -Wmissing-prototypes -Wpoi
[EMAIL PROTECTED] wrote:
> You're right .
> I will begin by migrate postgresql version.
> postgresql is now to 8.3 version . A lot of performance inprovements
> have been made in this last version .
> In any case I must do a pg_dump/pg_restore.
> So , Should I try directly 8.3 version or is it more
On Dec 19, 2007 4:23 PM, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> You're right .
> I will begin by migrate postgresql version.
> postgresql is now to 8.3 version . A lot of performance inprovements
> have been made in this last version .
> In any case I must do a pg_dump/pg_restore.
> So , Sh
Guillaume Lelarge a écrit :
[EMAIL PROTECTED] wrote:
You're right .
I will begin by migrate postgresql version.
postgresql is now to 8.3 version . A lot of performance inprovements
have been made in this last version .
In any case I must do a pg_dump/pg_restore.
So , Should I try directly 8.3
On Dec 19, 2007 5:17 PM, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> Guillaume Lelarge a écrit :
> > [EMAIL PROTECTED] wrote:
> >
> >> You're right .
> >> I will begin by migrate postgresql version.
> >> postgresql is now to 8.3 version . A lot of performance inprovements
> >> have been made in
Sorry to insist in this question, but now I was doing
some test and I notice that is a good idea to use
split utility.
This is because the output file got X bytes specified,
cut the rest of the line and will not import after.
In my example, I generated more than 2 files equal to
1MB. But already
Try splitting by line count instead of size:
-l, --lines=NUMBER
put NUMBER lines per output file
pg_dump | split -l 32000
You'll have to experiment to find how many lines will give you a roughly
appropriate size for your purposes.
Alternatively, another option is to get an USB external HDD
Hi ALL,
I am trying to use Copy command to copy data from table to a flat file.
Here is an example:
copy ( select * from employee where hire_date between begin_date and
end_date) to '/var/data/text.txt' delimiter ';';
But my problem is the query is not able to read variable begin_date and
Could you wrap it in a transaction block?
begin;
select *
into temp_table
from employee
where hire_date between begin_date and end_date;
copy temp_table to '/var/data/text.txt' delimiter ';';
commit;
THINK BEFORE YOU PRINT - Save paper if you don't really need to print this
*
Anyone know where I can find a full list of the strftime patterns that can be
used for log_filename ?
Thanks in advance..
/Kevin
---(end of broadcast)---
TIP 6: explain analyze is your friend
=?UTF-8?Q?Marcin?= <[EMAIL PROTECTED]> writes:
> Did anybody face the same problem during the compilation of postgresql 8.2.5
> on suse 10.2?
> ...
> dynalloc2.pgc: In function âmainâ:
> dynalloc2.pgc:55: internal compiler error: Segmentation fault
> Please submit a full bug report,
> with prepro
Kevin Kempter <[EMAIL PROTECTED]> writes:
> Anyone know where I can find a full list of the strftime patterns that can be
> used for log_filename ?
man strftime
or if you're feeling command-line-challenged, this should provide
info usable on most platforms:
http://www.opengroup.org/onlinepubs/0079
Try to set enviroment variable LANG to C value before compilation. If you
use sh shell you must execute: export LANG=C.
The gcc manual documents this. It's not a compiler bug.
Best regards.
2007/12/19, Marcin <[EMAIL PROTECTED]>:
>
> Did anybody face the same problem during the compilation of po
17 matches
Mail list logo
