Hallo,
I have been upgrading Postgresql version from 6.5 into 7.0 and slight
problems emerged, probably due to my insufficient knowledge:
1. In the older version, in psql, I could repeat SQL commands by means of
up-down keys - now I have to type everything again;
2. ODBC driver I have used to coop
"Jack" <[EMAIL PROTECTED]> writes:
> I have been upgrading Postgresql version from 6.5 into 7.0 and slight
> problems emerged, probably due to my insufficient knowledge:
> 1. In the older version, in psql, I could repeat SQL commands by means of
> up-down keys - now I have to type everything again
PostgreSQL 7.0 has been a huge success. Bug reports since release have
been so few that we thought our e-mail system wasn't working properly.
Turns out things are very quiet because the release is so stable.
So, those people waiting on the fence to try 7.0, go ahead. It is
ready for prime-time.
The 7.0-2 RPMset fixes the following:
1.) SPI headers are now the 7.0 set, and not the 6.5.3 set;
2.) pg_options default to NOT enable syslog, or extended query logging, as
syslogd has some issues with long queries (such as issued by psql's \d
command!);
3.) Alpha patches have returned
On Sat, 20 May 2000, Lamar Owen wrote:
> The 7.0-2 RPMset fixes the following:
> 1.) SPI headers are now the 7.0 set, and not the 6.5.3 set;
> 2.) pg_options default to NOT enable syslog, or extended query logging, as
> syslogd has some issues with long queries (such as issued by psql's \d
>
On Sun, 21 May 2000, Thomas Good wrote:
> On the GENERAL list the issue of firing up a server, and the silent flag
> used by the default redhatter 'postgresql' script in init.d came up.
Yes, I read the thread. I didn't write the original initscript -- but
hopefully have changed it to more your l
Hi!
I have installed postdrv.exe on a W98 machine ( it seems to be for 6.5
version ) and it works against the postgresql 7.0 under Linux.
I have linked some tables from MsAccess 2000 and the problem is that
sometimes when I try to update a row from MsAccess it does not let me do
it. It say
Lamar Owen <[EMAIL PROTECTED]> writes:
> The real problem with redirecting the postmaster output is the issue
> of log rolling, which is impossible to do in the 'classic'
> stderr/stdout redirect UNLESS you throw down postmaster when rolling
> the log (unless you know a trick I don't).
Yes. I th
On Mon, 22 May 2000 00:19:45 -0400 Tom Lane wrote:
> There needn't be a lot of code involved, we just need a
> well-thought-out spec for how it should work. Comments anyone?
I run postmaster under Dan Bernstein's "daemontools", which include
logging facilities:
http://cr.yp.to/daemon
Tom Lane wrote:
>
> Lamar Owen <[EMAIL PROTECTED]> writes:
> > The real problem with redirecting the postmaster output is the issue
> > of log rolling, which is impossible to do in the 'classic'
> > stderr/stdout redirect UNLESS you throw down postmaster when rolling
> > the log (unless you know
10 matches
Mail list logo
