The following bug has been logged online:
Bug reference: 2287
Logged by: Tanguy MOAL
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.7
Operating system: Linux Fedora Core 4
Description:Probably a translation error
Details:
When using the interactive mode :
Frank van Vugt <[EMAIL PROTECTED]> writes:
>> After you've created at least one temp table, you can look at the result
>> of "current_schemas(true)". There's no guarantee that the schema even
>> exists before you've created something...
> Is there a guaranteed order of the resulting array, i.e. i
Hi,
> In the first place, you are evidently running as superuser, which means
> that has_foo_privilege will ALWAYS say 't'
Ok, seems reasonable ;)
> (except possibly if the
> target object doesn't exist, in which case I think you get an error).
Yep, one does.
> In the second place, trying to
Frank van Vugt <[EMAIL PROTECTED]> writes:
> While running 2 sessions in different terminals for the same user, what
> happens in the second session here looks a bit weird:
In the first place, you are evidently running as superuser, which means
that has_foo_privilege will ALWAYS say 't' (except p
Hi,
While running 2 sessions in different terminals for the same user, what
happens in the second session here looks a bit weird:
=
=
db=# create temp table t_test (id int);
CREATE TABLE
db=# select table_schema from information_schema.tables
where table_name = 't_test
"Nicholas Vinen" <[EMAIL PROTECTED]> writes:
> Now, when I try to use PITR to restore the database on my test server, the
> PITR succeeds as normal, but I can not access the database with an error
> like:
> psql: FATAL: could not open relation 1663/16385/605464: No such file or
> directory
This
"David Sauer" <[EMAIL PROTECTED]> writes:
> PostgreSQL version: 8.1.2, 8.1.3
> Operating system: Linux (libc6), debian
> Description:Wrong index creation with cs_CZ locales and HYPHEN
You've probably gotten bit by the 8.1.2 changes in locale-dependent
sorting. Try REINDEXing the affecte
On Mon, Feb 27, 2006 at 11:52:19AM +, [EMAIL PROTECTED] wrote:
> if the server shuts down abrupotly because of power failuar or any other
> cause then the sequences tend to skip few numbers.
> After restarting the postgresql server the nextval of sequence doest match
> with the last number.
ht
[EMAIL PROTECTED] wrote:
> if the server shuts down abrupotly because of power failuar or any other
> cause then the sequences tend to skip few numbers.
> After restarting the postgresql server the nextval of sequence doest match
> with the last number.
This is per design, i.e. not a bug.
--
Al
The following bug has been logged online:
Bug reference: 2285
Logged by: Nicholas Vinen
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: Gentoo Linux x86
Description:Can not access database after successful PITR - file
naming problems
Detai
The following bug has been logged online:
Bug reference: 2283
Logged by:
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Windows XP Home Edition SP2
Description:VS .NET 2003 connection problem
Details:
Hello,
In Visual Studio .NET 2003,
The following bug has been logged online:
Bug reference: 2286
Logged by: David Sauer
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.2, 8.1.3
Operating system: Linux (libc6), debian
Description:Wrong index creation with cs_CZ locales and HYPHEN
Details:
I h
The following bug has been logged online:
Bug reference: 2284
Logged by:
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.3.2
Operating system: linux
Description:missing sequence number
Details:
if the server shuts down abrupotly because of power failuar or a
13 matches
Mail list logo
