"Carsten" <[EMAIL PROTECTED]> writes:
> Were there any changes which made the pgsql server stricter in requiring
> that all table-spaces exist on start-up?
Not that I can think of --- except that startup for crash recovery has
always expected everything to be accessible. If that's not what you're
"Christian Gonzalez" <[EMAIL PROTECTED]> writes:
> Description:Partitioning has problem with timestamp and timestamptz
> data types
In your example as given, you partition the table on "logdate", and then
add an unrelated column "logdatet" and seem to expect that the system
will think that
I am reporting a bug on duplicate rows on primary key. Below is the
information:
Thank you for your bug report
The report (reference: 3222) will be forwarded to the development team for
further investigation.
http://wwwmaster.postgresql.org/system/handler.php?page=submitthanks&lang=en
&action=s
The following bug has been logged online:
Bug reference: 3232
Logged by: Carsten
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.3
Operating system: Windows XP SP 2
Description:Regression: pgsql server startup problem with encrypted
partitions
Details:
I am
The following bug has been logged online:
Bug reference: 3235
Logged by: Christian Gonzalez
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.1
Operating system: Red Hat 4.1.1-30
Description:Partitioning has problem with timestamp and timestamptz
data types
Det
The following bug has been logged online:
Bug reference: 3234
Logged by: Jonathan Vanasco
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.3
Operating system: freebsd 6.1 , osx 10.4.9
Description:pg_dump uses the first version of a primary key's name
when gene
The following bug has been logged online:
Bug reference: 3233
Logged by: Dmitry Belyavsky
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.6
Operating system: FreeBSD 6
Description:Trigger checks failed on concurrent transactions
Details:
Greetings!
I have
The following bug has been logged online:
Bug reference: 3236
Logged by: Christian Gonzalez
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.1
Operating system: Red Hat 4.1.1-30
Description:Partitioning has problem with timestamp and timestamptz
data type
Deta
On Mon, Apr 16, 2007 at 04:18:02AM +, Kazuhiro Inaoka wrote:
>
> The following bug has been logged online:
>
> Bug reference: 3228
> Logged by: Kazuhiro Inaoka
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1
> Operating system: linux
> Description:Lin
Russell Smith wrote:
> Alvaro Herrera wrote:
> >Jeff Davis wrote:
> >
> >
> >>CREATE ROLE test_role
> >> NOSUPERUSER INHERIT NOCREATEDB NOCREATEROLE;
> >>
> >>CREATE ROLE invalid_grantor
> >> SUPERUSER INHERIT NOCREATEDB NOCREATEROLE;
> >>
> >>SET ROLE invalid_grantor;
> >>GRANT "postgres" TO
Alvaro Herrera wrote:
Jeff Davis wrote:
CREATE ROLE test_role
NOSUPERUSER INHERIT NOCREATEDB NOCREATEROLE;
CREATE ROLE invalid_grantor
SUPERUSER INHERIT NOCREATEDB NOCREATEROLE;
SET ROLE invalid_grantor;
GRANT "postgres" TO "test_role";
SET ROLE postgres;
select * from pg_roles;
11 matches
Mail list logo