Greg Sabino Mullane wrote:
> real_psql --set AUTOCOMMIT=OFF $@
I have stumbled over this myself: psql is case-sensitive here at the moment,
so it must be --set AUTOCOMMIT=off.
Best Regards,
Michael
---(end of broadcast)---
TIP 8: explain analyze i
Except transparency...
John Sidney-Woollett
Peter Eisentraut wrote:
John Sidney-Woollett wrote:
Why not create this file during the "make install", and explicitly
set the current/standard default options (for psql) in the
$PREFIX/share/psqlrc file?
Because it would take up space, computing power,
John Sidney-Woollett wrote:
> Why not create this file during the "make install", and explicitly
> set the current/standard default options (for psql) in the
> $PREFIX/share/psqlrc file?
Because it would take up space, computing power, and attention without
achieving anything.
--
Peter Eisentra
Why not create this file during the "make install", and explicitly set
the current/standard default options (for psql) in the
$PREFIX/share/psqlrc file?
If the file is deleted or not found then the current/standard default
options would still apply - but atleast the default are there for all to
Lars Haugseth wrote:
> * Michael Paesold:
> | Peter Eisentraut wrote:
> | > Lars Haugseth wrote:
> | > > Version 8.0.0beta2 supports a global configuration file. It's should
> | > > be located in '~postgres/etc/pgsql'.
> | >
> | > That would be pretty useless, since normal users often don't have re
* Michael Paesold:
| Peter Eisentraut wrote:
| > Lars Haugseth wrote:
| > > Version 8.0.0beta2 supports a global configuration file. It's should
| > > be located in '~postgres/etc/pgsql'.
| >
| > That would be pretty useless, since normal users often don't have read
| > access to another user's hom
Peter Eisentraut wrote:
> Lars Haugseth wrote:
> > Version 8.0.0beta2 supports a global configuration file. It's should
> > be located in '~postgres/etc/pgsql'.
>
> That would be pretty useless, since normal users often don't have read
> access to another user's home directory.
Further up in th
Lars Haugseth wrote:
> Version 8.0.0beta2 supports a global configuration file. It's should
> be located in '~postgres/etc/pgsql'.
That would be pretty useless, since normal users often don't have read
access to another user's home directory.
--
Peter Eisentraut
http://developer.postgresql.org/
Thanks to you and Bruce for the info.
I'll live with modifying the ~/.psqlrc file until we move to version 8.
John Sidney-Woollett
Lars Haugseth wrote:
* Peter Eisentraut:
| John Sidney-Woollett wrote:
| > Any ideas why the global file doesn't work?
|
| There is no support for a global configuratio
Thanks - I'll live with modifying the ~/.psqlrc file until we move to
version 8.
John Sidney-Woollett
Lars Haugseth wrote:
* Peter Eisentraut:
| John Sidney-Woollett wrote:
| > Any ideas why the global file doesn't work?
|
| There is no support for a global configuration file at this time. I
| s
* Peter Eisentraut:
| John Sidney-Woollett wrote:
| > Any ideas why the global file doesn't work?
|
| There is no support for a global configuration file at this time. I
| suggested that you *implement* it.
Version 8.0.0beta2 supports a global configuration file. It's should be
located in '~post
> To ease any pain, what about a configuration setting for the build
> script for postgres (and psql) which changes the default behaviour for
> the AUTOCOMMIT setting.
I really agree on the need for a posibility to set autocommit = off
*regardless* of the client:
On a system using both psql, php
I can see this is going nowhere fast! :)
I'd like to see a global setting that I could change, not one on a user
by user basis...
I'd also like a message in the Welcome banner telling me what the
current AUTOCOMMIT setting is...
John Sidney-Woollett
Peter Eisentraut wrote:
John Sidney-Woollett
John Sidney-Woollett wrote:
> If a config switch was available for the build process that could
> preserve the "old" behavior - it wouldn't really pose a problem for
> existing users migrating their systems to v8 provided they set the
> switch appropriately.
Such a switch exists: you put \set AUTO
I agree with you 100% about this - whoever it won't affect new users
starting with v8 (including many new Windows users), and those migrating
from other dbs (like Oracle).
If a config switch was available for the build process that could
preserve the "old" behavior - it wouldn't really pose a p
John Sidney-Woollett wrote:
> It will break any newly compiled version of psql expecting to work to
> the old behaviour. It won't affect anyone using an older version of
> postgres or psql (ie pre version 8).
Of course there are no backward compatibility issues when you keep using
the old version
No it won't!
It will break any newly compiled version of psql expecting to work to
the old behaviour. It won't affect anyone using an older version of
postgres or psql (ie pre version 8).
To ease any pain, what about a configuration setting for the build
script for postgres (and psql) which cha
John Sidney-Woollett <[EMAIL PROTECTED]> writes:
> With the advent of postgres v8, would it be possible to change the
> default behaviour of psql from AUTOCOMMIT=ON to AUTOCOMMIT=OFF ?
If that's what you want, set it in your ~/.psqlrc.
regards, tom lane
-
John Sidney-Woollett wrote:
> With the advent of postgres v8, would it be possible to change the
> default behaviour of psql from AUTOCOMMIT=ON to AUTOCOMMIT=OFF ?
Absolutely not. This will break every psql use in existence.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---
With the advent of postgres v8, would it be possible to change the
default behaviour of psql from AUTOCOMMIT=ON to AUTOCOMMIT=OFF ?
Although this might break backward compatibility, it might be acceptable
on the basis that v8 is such a major release.
Also adding a new command line parameter to
20 matches
Mail list logo
