On Wednesday, 10 November 2004 18:28, Tom Lane wrote:
> Achilleus Mantzios <[EMAIL PROTECTED]> writes:
> > Just a very naive thought
> > Wouldn't make more sense to allow nested begin/commit/rollback blocks?
>
> We actually had it working that way initially, but changed to the
> spec-defined be
On Wed, Nov 10, 2004 at 09:18:21AM +, Sam Mason wrote:
>
> mkfifo db1
> psql -h "db1" -t -q -c "$query" > db1
> mkfifo db2
> psql -h "db2" -t -q -c "$query" > db2
> diff -u -0 db1 db2
This should work for small data sets, but the OP said the tables
were about 5G. Unless you use a c
Its works if I specify the ipaddress of each client which is being
connecting to the server.
Its hard to do it on a DHCP network . Any roundabouts ?
- Goutam
> -Original Message-
> From: Richard Huxton [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, November 10, 2004 1:30 PM
> To: Goutam Pa
David B wrote:
My first time using unicode. Based on reading other messages I think I've
got it all setup correctly but still have prob.
Running: psql 7.3.6-RH
[snip]
For both I get the same results when I try to:
INSERT INTO airport_code ( airport_name, airport_code ) values ( 'Zurich
(Zürich) - K
Goutam Paruchuri wrote:
My understanding was it means ip range of 1 to 254.
192.168.2.1 to 192.168.1.254
No, it refers to the number of bits. You can use either of:
192.168.2.0 255.255.255.0
192.168.2.0/24
Both of these cover the range:
192.168.2.1 - 192.168.1.255
Might be worth searching for
The IP of the client machine aim connecting from is 192.168.2.123
Which is greater than 32.
Thanks !
- Goutam
> -Original Message-
> From: Richard Huxton [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, November 10, 2004 12:19 PM
> To: Goutam Paruchuri
> Cc: [EMAIL PROTECTED]
> Subject: Re
My understanding was it means ip range of 1 to 254.
192.168.2.1 to 192.168.1.254
> -Original Message-
> From: Richard Huxton [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, November 10, 2004 12:19 PM
> To: Goutam Paruchuri
> Cc: [EMAIL PROTECTED]
> Subject: Re: [SQL] Error In connectio
Achilleus Mantzios <[EMAIL PROTECTED]> writes:
> Just a very naive thought
> Wouldn't make more sense to allow nested begin/commit/rollback blocks?
We actually had it working that way initially, but changed to the
spec-defined behavior, because (a) it wasn't standard, and (b) it
was confusing.
Goutam Paruchuri wrote:
Hello,
I get an error in my log when connecting to postgres server on Windows.
Postgres version : 8.0.0-beta4
LOG TEXT
2004-11-10 11:22:47 LOG: invalid entry in file "C:/Program
Files/PostgreSQL/8.0.0-beta4/data/pg_hba.conf" at line 64, token
"192.168.2.1/254"
2004-11-10
My first time using unicode. Based on reading other messages I think I've
got it all setup correctly but still have prob.
Running: psql 7.3.6-RH
$ psql -l
List of databases
Name| Owner | Encoding
---+--+---
devdb | devuser | UNICODE
template0 | pos
Hello,
I get an error in my log when connecting to postgres server on Windows.
Postgres version : 8.0.0-beta4
LOG TEXT
2004-11-10 11:22:47 LOG: invalid entry in file "C:/Program
Files/PostgreSQL/8.0.0-beta4/data/pg_hba.conf" at line 64, token
"192.168.2.1/254"
2004-11-10 11:22:47 FATAL: missi
Achilleus Mantzios wrote:
> In other words, now with savepoints, BEGIN; COMMIT; ROLLBACK;
> can be replaced with
> SAVEPOINT foo; RELEASE foo; ROLLBACK TO foo; respectively.
>
> If only transactions weren't a requirement for SAVEPOINTs,
> what would we then need BEGIN; COMMIT; ROLLBACK; for?
Note
Achilleus Mantzios wrote:
> Wouldn't make more sense to allow nested begin/commit/rollback
> blocks?
Possibly. But that consideration would have been more relevant about 6
years ago when they wrote the SAVEPOINT syntax into the SQL standard.
:)
--
Peter Eisentraut
http://developer.postgresql.
O Peter Eisentraut έγραψε στις Nov 10, 2004 :
> Achilleus Mantzios wrote:
> > Wouldn't make more sense to allow nested begin/commit/rollback
> > blocks?
>
> Possibly. But that consideration would have been more relevant about 6
> years ago when they wrote the SAVEPOINT syntax into the SQL stand
Okay, I see you're speaking about pgsql 8.0
What about 7.4?
Andy.
- Original Message -
From: "Achilleus Mantzios" <[EMAIL PROTECTED]>
To: "Michael Fuhr" <[EMAIL PROTECTED]>
Cc: "Riccardo G. Facchini" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>; "Theodore Petrosky" <[EMAIL PROTECTED]>; "Andr
O Michael Fuhr έγραψε στις Nov 10, 2004 :
> On Wed, Nov 10, 2004 at 12:45:19AM -0800, Riccardo G. Facchini wrote:
>
> > Sorry, but I understand that your example is not really about nested
> > transactions, but about sequential transactions.
>
> Here's a more elaborate example. If this doesn't
On Wed, Nov 10, 2004 at 12:45:19AM -0800, Riccardo G. Facchini wrote:
> Sorry, but I understand that your example is not really about nested
> transactions, but about sequential transactions.
Here's a more elaborate example. If this doesn't demonstrate the
capability you're looking for, then ple
Gregory S. Williamson wrote:
>Is there any way to do this from inside postgres that anyone knows of
>? I looked through the manual and the contrib stuff and didn't see
>much ...
Not really "inside postgres"; but could you do something like:
mkfifo db1
psql -h "db1" -t -q -c "$query" > db1
m
Sorry, but I understand that your example is not really about nested
transactions, but about sequential transactions.
so, the primary question remains:
how to commit/rollback them ?
--- Michael Fuhr <__> wrote:
> On Wed, Nov 10, 2004 at 09:23:02AM +0300, sad wrote:
> > On Tuesday 09 November 20
19 matches
Mail list logo
