Well, you'll see the status of the last UPDATE executed due to a rule
... but that doesn't mean it couldn't have updated zero rows. It might
be worth pointing out here that conditional rules insert queries that
have the condition added to their WHERE clause; if the condition is
false then no rows
The following bug has been logged online:
Bug reference: 2137
Logged by: Chander Ganesan
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.1
Operating system: SLES 9 - linux 2.6.5-7.97-default #1 Fri Jul 2 14:21:59
UTC 2004 i686 i686 i386 GNU/Linux
Description:
The following bug has been logged online:
Bug reference: 2135
Logged by: Carlos del Cacho
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.1
Operating system: Win2k
Description:system error 182 while loading ODBC driver
Details:
I am using the win32 binary d
The following bug has been logged online:
Bug reference: 2136
Logged by: Robert Osowiecki
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.1
Operating system: Linux 2.6.14-gentoo-r5 #2 SMP Thu Dec 22 11:58:01 CET
2005 i686 Intel(R) Xeon(TM) CPU 3.20GHz GenuineIntel G
Andreas Pflug wrote:
> Tom Lane wrote:
> > Andreas Pflug <[EMAIL PROTECTED]> writes:
> >
> >>Is COPY foo TO STDOUT BINARY supposed to work?
> >
> >
> > I don't think psql will do anything particularly sane with binary copy
> > data, if that's what you meant.
>
> echo "COPY foo TO STDOUT BINARY;
Hi,
I was running a manual vacuum through pgadmin 1.4.1 on a database and my
connection to the database was lost during it. I reconnected to the database,
went to Tools->Server Status->Log File and there is an entry that says:
"This application has requested the Runtime to terminate in an unus
Martin Pitt <[EMAIL PROTECTED]> writes:
> Tom Lane [2005-12-29 22:20 -0500]:
>> I think the only real problem here is that the role ends up with
>> NOLOGIN set, which we could probably fix by reordering the commands;
> It will also lead to confusion, especially if the user is not in the
> group wi
Hi!
Tom Lane [2005-12-29 22:20 -0500]:
> Martin Pitt <[EMAIL PROTECTED]> writes:
> > I recently got a rather interesting Debian bug [1]: When upgrading a
> > pre-8.1 database to 8.1, the upgrade messes up permissions if the old
> > database had users and groups with the same name. Since in 8.1 the
Hi Bruce!
Bruce Momjian [2005-12-29 20:06 -0500]:
> I think we decided that the number of users who have this problem and
> would be using upgraded pg_dumpall to upgrade to 8.1 is too small. (If
> we had realized this problem pre-8.1, it would have been great to have
> fixed it.) In your upgrad
