On Wed, 2004-03-03 at 15:00, Sally Sally wrote:
> I wanted to dump the contents of one table to another (with a different
> name) within the same database. I am looking at pg_restore and it doesn't
> seem to have the option of specifying the name of the table we want to dump
> to, only the name
On Wed, 3 Mar 2004, Palle Girgensohn wrote:
> Hi,
>
> Just realized that man pages are not installed. Reason is that
> doc/man.tar.gz does not exists, but Makefile expects it. instead, there is
> a doc/man-7.3.tar.gz...
Damn ... its a quick/easy change on my end, but I had an argument once way
ba
Thinking some more, I say re-package. Those using this file for automatic
packaging have not fetched it yet, hopefully...
/Palle
--On Wednesday, March 03, 2004 11:21:28 -0400 "Marc G. Fournier"
<[EMAIL PROTECTED]> wrote:
On Wed, 3 Mar 2004, Palle Girgensohn wrote:
Hi,
Just realized that man
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> On Wed, 3 Mar 2004, Palle Girgensohn wrote:
>> Just realized that man pages are not installed. Reason is that
>> doc/man.tar.gz does not exists, but Makefile expects it. instead, there is
>> a doc/man-7.3.tar.gz...
> Damn ... its a quick/easy change
Phil Campaigne wrote:
Hi Ron,
I had a couple of questions on your instructions:
1. what is this for?
>#make install-all-headers
According to the docs you need it if you are going to create your own
functions, however the documentation is a bit *vague*. "If you plan to
do any server-side program
> hi all
> Are there any other docs about tsearch2 except for the 3 docs in
> \contrib\tsearch2\docs
>
> i want some tech docs on tsearch2 thank all
See http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/
George Essig
---(end of broadcast)---
On Wed, 3 Mar 2004, Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > On Wed, 3 Mar 2004, Palle Girgensohn wrote:
> >> Just realized that man pages are not installed. Reason is that
> >> doc/man.tar.gz does not exists, but Makefile expects it. instead, there is
> >> a doc/man-7.
repackaged ... let me know if you see any other errors ...
On Wed, 3 Mar 2004, Palle Girgensohn wrote:
> Thinking some more, I say re-package. Those using this file for automatic
> packaging have not fetched it yet, hopefully...
>
> /Palle
>
> --On Wednesday, March 03, 2004 11:21:28 -0400 "Marc
On Wednesday 03 March 2004 11:03 am, Marc G. Fournier wrote:
> On Wed, 3 Mar 2004, Tom Lane wrote:
> > "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > > On Wed, 3 Mar 2004, Palle Girgensohn wrote:
> > >> Just realized that man pages are not installed. Reason is that
> > >> doc/man.tar.gz does no
b is often mistaken for beta, and I believe it is already too late, it is
out at the main server?
/Palle
--On Wednesday, March 03, 2004 11:26:03 -0500 "Matthew T. O'Connor"
<[EMAIL PROTECTED]> wrote:
On Wednesday 03 March 2004 11:03 am, Marc G. Fournier wrote:
On Wed, 3 Mar 2004, Tom Lane wrot
Harald Fuchs wrote:
In article <[EMAIL PROTECTED]>,
"scott.marlowe" <[EMAIL PROTECTED]> writes:
On Tue, 2 Mar 2004, [UTF-8] PauloviÃÂ Michal wrote:
how you solve the problem with multilevel autoicrement?
In MySQL you create table with col1, col2. Col 2 is AUTOICRE
Hello,
I have a problem with this simple query :
explain select * from ref_artikel a where a.artnr in ( 351275 , 351346 ,
293082 ) LIMIT 20 OFFSET 0 ;
QUERY PLAN
-
On Wed, Mar 03, 2004 at 18:12:18 +0100,
Paulovi?? Michal <[EMAIL PROTECTED]> wrote:
> You don't build secent level unique
> You have to create uniqe index under both levels (first and second)
> together. But in MySQL there is no problem.
> I alredy have table with mulitlevel autoincrement (in My
Gellert, Andre wrote:
Hello,
I have a problem with this simple query :
explain select * from ref_artikel a where a.artnr in ( 351275 , 351346 ,
293082 ) LIMIT 20 OFFSET 0 ;
QUERY PLAN
Mihai RUSU wrote:
[ PGP not available, raw data follows ]
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi
>
> I was working recently on a mid-layer in my current projects for
> abstraction of SQL backends (curently for mysql and pgsql only) and found
> out that the libpq synonime of mysq
We've implemented a 5D box data type and have implemented both RTree and
GiST access methods under PostgresSQL 7.4 and PostgresSQL 7.4.1. The 5D
box internally looks like:
struct Box5D{
float
minBounds[5];
float
maxBounds[5];
};
and so takes up 40 bytes and is of fixed le
On Wed, 3 Mar 2004, [iso-8859-15] Hervé Piedvache wrote:
> Hi,
>
> I have may be a stupid question, but I'm a little surprised with some explains
> I have, using date fields ...
>
> I would like to understand exactly when index are used ...
> I'm using PostgresQL 7.4.1
>
> I have a table with
On Wed, 3 Mar 2004, [UTF-8] Paulovič Michal wrote:
> Yes I know,
>
> But how you do this at PgSQL
OK, I just read the response where someone showed me how to make such a
table in mysql. What an odd, and non-intuitive behaviour that is.
Anyway, first off, upgrade your version of postgresql
Bruno Wolff III wrote:
On Wed, Mar 03, 2004 at 18:12:18 +0100,
Paulovi?? Michal <[EMAIL PROTECTED]> wrote:
You don't build secent level unique
You have to create uniqe index under both levels (first and second)
together. But in MySQL there is no problem.
I alredy have table with mulitlevel au
On Wed, Mar 03, 2004 at 06:45:56AM +0100, Paulovi?? Michal wrote:
> Yes I know,
>
> But how you do this at PgSQL
You have to lock the table exclusively, get the max value for your
particular "id1", increment it, insert the row, and commit:
begin;
lock table test in exclusive mode;
insert int
FYI,
It'd be nice if the error message from a REFERENCES
constraint mentioned the column name into which
the bad data was attempted to be inserted.
In PostgreSQL 7.3:
sandbox=> insert into foo (id, b) values (3, 2);
ERROR: b_is_fkey referential integrity violation - key referenced from
foo not
After several fixes were backpatches to the 7_3_STABLE branch, we have now
released a 7.3.6. As the list of Changes since 7.3.5 is quite small, they
are included in this email:
* Revert erroneous changes in rule permissions checking
* Repair incorrect order of operations in GetNewTrans
Michael Chaney <[EMAIL PROTECTED]> writes:
> begin;
> lock table test in exclusive mode;
> insert into test values (1,(select max(id2) from test where id1=1)+1);
> commit;
> It's not pretty, and it'll probably slow down as the table grows.
As-is, that will definitely get pretty slow on large tabl
Phil Campaigne wrote:
Hi Ron,
I had a couple of questions on your instructions:
1. what is this for?
>#make install-all-headers
According to the docs you need it if you are going to create your own
functions, however the documentation is a bit *vague*. "If you plan to
do any server-side progr
I am currently working on a Java web application in which we are making
use of the JDBC driver for Postgres 7.4.1. Part of our application
allows the administrators to manage a large number of small images,
most of them not exceeding 5KB. There is about a gigabyte of these
small files. We're
"Karl O. Pinc" <[EMAIL PROTECTED]> writes:
> It'd be nice if the error message from a REFERENCES
> constraint mentioned the column name into which
> the bad data was attempted to be inserted.
You mean like this?
regression=# create table foo (pk int primary key);
NOTICE: CREATE TABLE / PRIMARY K
The access is open !!!
password: 85464
<>
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
Eric Davies <[EMAIL PROTECTED]> writes:
> We've looked at the contrib/cube code, but it's also a variable length
> parameter, and it uses a very different parameter passing mechanism.
Different how? I have a hard-to-pin-down intuition that your problem is
closely associated with this issue, but
28 matches
Mail list logo
