Your patch has been added to the PostgreSQL unapplied patches list at:
http://candle.pha.pa.us/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
> David Daney ([EMAIL PROTECTED]) reports a bug with a severity of 3
> The lower the number the more severe it is.
>
> Shor
David Daney ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
Another security issue with the JDBC driver.
Long Description
The JDBC driver requires
permission java.net.SocketPermission "host:port", "connect";
in the policy f
Hi!
I forgot to add:
It DOESN'T happen in PostgreSQL 7.1beta3
It DOEShappen in PostgreSQL 7.1beta4 (but on a different machine)
Greetings,
tom
--
.signature: Too many levels of symbolic links
---(end of broadcast)---
TIP 3: if posting/readi
Hi!
I'm using PostgreSQL 7.1.3 on Intel PIII, Linux 2.4.8, Slackware 8.0,
compiled with egcs 2.91.66 (the same on 7.1.2 / 2.95.3).
I'm encountering very strange deadlock situation. Strange, because after
this deadlock occurs, even with no active postgres processes (postmaster only),
when I conne
Bruce Momjian writes:
> Let me see if I follow here. If I am in the Eastern timezone and enter
> a time for 9pm, 1/1/1850, and someone else in the Central timezone
> enters the same time, if I look at the two dates from the Eastern
> timezone I will see mine as 9pm and the other as 10pm?
That's
Your patch has been added to the PostgreSQL unapplied patches list at:
http://candle.pha.pa.us/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
> David Daney ([EMAIL PROTECTED]) reports a bug with a severity of 3
> The lower the number the more severe it is.
>
> Shor
> Tom Lane writes:
>
> > Timezone handling in PG is dependent on the underlying OS' timezone
> > database, which doesn't go back further than 1901 in any Unix that
> > I've heard of. You should realize of course that the very notion of
> > timezone was only standardized in the 1800s, so attachin
[EMAIL PROTECTED] writes:
> Now i will create two views:
> P1V:
> select order_id as id1, count(*) as count1 from order_item where state=1 group by
>order_id;
> P2V:
> select order_id as id2, count(*) as count2 from order_item where state=2 group by
>order_id;
Grouped views don't work very w
> PostgreSQL 7.0.2 on i686-pc-linux-gnu, compiled by gcc egcs-2.91.66
>
> wrong results when joining views.
Upgrade to the latest version (7.1.3).
--
Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter
---(end of broadcast)---
Vladimir () reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
Long Description
Sample Code
No file was uploaded with this report
---(end of broadcast)---
TIP 3: if posting/reading through Usene
Vladimir Bezak ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
joining views
Long Description
PostgreSQL 7.0.2 on i686-pc-linux-gnu, compiled by gcc egcs-2.91.66
wrong results when joining views.
Sample Code
table ORDER_
Tom Lane writes:
> Timezone handling in PG is dependent on the underlying OS' timezone
> database, which doesn't go back further than 1901 in any Unix that
> I've heard of. You should realize of course that the very notion of
> timezone was only standardized in the 1800s, so attaching a timezone
12 matches
Mail list logo
