Alvaro Herrera wrote:
In my opinion, the need
for running tests outside the test dir is not very strong (or we would
have heard complaints before), and thus the solution is to remove
--inputdir and --outputdir.
Attached is a patch that removes --inputdir and --outputdir. I still
prefere the fi
Alvaro Herrera wrote:
Today, using --inputdir in pg_regress does not work for any other value
than something that resolves to cwd, since it will write a file to
"./sql", but try to read the same file from "/sql".
Maybe I'm missing something, but I don't see any reason why this is a
scenario
Alvaro Herrera wrote:
Jorgen Austvik - Sun Norway wrote:
The attached patch makes pg_regress write converted files to
/sql and /expected, which is one way to make it read
and write to the same directory. Tested on Solaris x86 with pgsql "make
check" and standalone.
I think t
Hi,
with regards to --inputdir, --srcdir, --outputdir and --schedule,
pg_regress does something like this:
convert files in /input, and place them in ./sql
convert files in /output, and place them in ./expected
read schedule from
for each test in schedule:
read test from /sql/.sql
read
Alvaro Herrera wrote:
Maybe, or maybe not. Do these platforms all have Perl?
gypsy_moth Solaris 8 SUN Studio 8 spar
If the moths don't have perl, we'll add it, no problem - don't let that
stop anything.
(On a separate note, we have had some problems internally with DNS, so
some reporting
Tom Lane wrote:
Jorgen Austvik - Sun Norway <[EMAIL PROTECTED]> writes:
we would like to be able to use and ship pg_regress and the PostgreSQL
test suite independently of the PostgreSQL build environment, for
testing and maybe even as a separate package to be build and shipped
with the
Hi.
pg_regress has a --dbname option (which actually take a list of database
names):
--dbname=DB use database DB (default \"regression\")
... but the PostgreSQL regression test suite does not really support this:
[EMAIL PROTECTED]:regress] ggrep -R "regression" sql/* | grep -
Hi,
we would like to be able to use and ship pg_regress and the PostgreSQL
test suite independently of the PostgreSQL build environment, for
testing and maybe even as a separate package to be build and shipped
with the OS for others to test their setup. Does this sound like a sane
and OK thin
Tom Lane wrote:
It looks like gypsy_moth has been failing like this:
creating directory
/export/home/tmp/pg-test/build-suncc/HEAD/pgsql.21325/src/test/regress/./tmp_check/data
... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers/max_f
Tom Lane wrote:
This is unfortunate and surprising, since that patch was intended to
prevent compilers from making unsafe alignment assumptions, but it sure
looks like this compiler has instead added a new one. Could you poke
into it --- at least get a stack trace from the core dump?
Forgot so
Jorgen Austvik - Sun Norway wrote:
Problem between keyboard and chair, in doc, libpq, psql or elsewhere?
Sorry, the psql documentation is clear on this:
\lo_export
Note that this is subtly different from the server function lo_export,
which acts with the permissions of the user that the
Hi,
The PostgreSQL 8.3 documentation[1] says this about lo_export and
lo_import paths and servers:
Import:
Note that the file is read by the client interface library, not by
the server; so it must exist in the client file system and be
readable by the client application.
Export:
Tommy wrote:
How exactly can I check to see if psql returns ZERO to the "shell"? What do
I test for? If(Psql.exe)? or is there a variable I can check to see if it
has been set?
If you are running Delphi on Windows (the MsgBox makes me guess so),
take a look here:
http://delphi.about.com/od/w
13 matches
Mail list logo
