On Wed, Jul 16, 2003 at 16:31:24 -0400,
Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> On Wed, Jul 16, 2003 at 01:57:41PM -0500, Thomas Swan wrote:
> > Does anyone have recent archives of the pgsql-hackers list in mbx or
> > flat file format?
> >
> > I know that I can search through the website o
Gavin Sherry <[EMAIL PROTECTED]> writes:
> Shouldn't we be detecting problems with the following (haven't seen
> mention of it):
> template1=# insert into b values('1000-12-01 23:23:23');
> INSERT 555183 1
> template1=# select * from b;
> ERROR: Unable to format timestamp; internal coding erro
I returned Monday night from O'Reilly and LinuxTag. I have several
things to do this week:
read backlog of email
create 7.4 changes list
apply outstanding patches
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (6
=?ISO-8859-1?Q?Hans-J=FCrgen_Sch=F6nig?= <[EMAIL PROTECTED]> writes:
> question is: How do I find out when a query starts? Inside a table
> function I can call SRF_IS_FIRSTCALL() to see when it is called first.
> Is there an easy way to check that inside an "ordinary" C function
> returning just
--On Thursday, July 17, 2003 14:24:03 -0400 Robert Treat
<[EMAIL PROTECTED]> wrote:
On Thu, 2003-07-17 at 14:15, Larry Rosenman wrote:
--On Thursday, July 17, 2003 18:11:25 + Rod Taylor <[EMAIL PROTECTED]>
wrote:
> On Wed, 2003-07-16 at 21:16, Tom Lane wrote:
>> Larry Rosenman <[EMAIL PRO
On Thu, 2003-07-17 at 14:15, Larry Rosenman wrote:
>
>
> --On Thursday, July 17, 2003 18:11:25 + Rod Taylor <[EMAIL PROTECTED]> wrote:
>
> > On Wed, 2003-07-16 at 21:16, Tom Lane wrote:
> >> Larry Rosenman <[EMAIL PROTECTED]> writes:
> >> > Is the patches list working?
> >>
> >> I saw someth
Here is how I doi it when I need to...
BEGIN;
CREATE TEMP SEQUENCE row_num;
SELECT next_val('row_num'), relname FROM pg_class LIMIT 3;
ROLLBACK;
You could also do this with a Set Returning Fucntion so that it returns the
nextval in a simular way
On Thursday 17 July 2003 08:03, Hans-Jürgen Sch
On Thu, 2003-07-17 at 14:11, Rod Taylor wrote:
> On Wed, 2003-07-16 at 21:16, Tom Lane wrote:
> > Larry Rosenman <[EMAIL PROTECTED]> writes:
> > > Is the patches list working?
> >
> > I saw something come through yesterday from Rod.
>
> Which is funny because it's not in the archives and I didn't
--On Thursday, July 17, 2003 18:11:25 + Rod Taylor <[EMAIL PROTECTED]> wrote:
On Wed, 2003-07-16 at 21:16, Tom Lane wrote:
Larry Rosenman <[EMAIL PROTECTED]> writes:
> Is the patches list working?
I saw something come through yesterday from Rod.
Which is funny because it's not in the archive
On Wed, 2003-07-16 at 21:16, Tom Lane wrote:
> Larry Rosenman <[EMAIL PROTECTED]> writes:
> > Is the patches list working?
>
> I saw something come through yesterday from Rod.
Which is funny because it's not in the archives and I didn't receive the
message to my own inbox.
signature.asc
Descrip
Tom Lane kirjutas N, 17.07.2003 kell 19:49:
> Ugh. The reason we hadn't seen this happen in the field was that it is
> a bug I introduced in a patch two months ago :-(
>
> 7.3.3 will in fact fail to start up, with the above error, any time the
> last record of the WAL file ends exactly at a page
Hannu Krosing <[EMAIL PROTECTED]> writes:
> WHen running PostgreSQL 7.3.3-1 (from rpm's) on Redhat 9.0 I got the
> following in logs and the postmaster will not start up.
> PANIC: XLogWrite: write request 0/30504000 is past end of log
> 0/30504000
Ugh. The reason we hadn't seen this happen in th
I had a brief look at DB2's row_number function which seems to be pretty
useful.
What it does is:
test=# SELECT row_number(), relname FROM pg_class LIMIT 3;
row_number |relname
+
1 | pg_description
2 | pg_group
3 | pg_proc
(3 rows)
Th
On Wed, 16 Jul 2003, Alvaro Herrera wrote:
> On Wed, Jul 16, 2003 at 03:35:51PM -0500, Larry Rosenman wrote:
>
> > --On Wednesday, July 16, 2003 16:31:24 -0400 Alvaro Herrera
> > <[EMAIL PROTECTED]> wrote:
> >
> > >On Wed, Jul 16, 2003 at 01:57:41PM -0500, Thomas Swan wrote:
> > >>Does anyone h
On Mon, 14 Jul 2003, Tom Lane wrote:
> Probably the only real solution is to implement DROP-CASCADE-like
> checking when a privilege is revoked. Seems like rather a lot of
> work :-(
Yes and yes. That's why the SQL standard goes on for pages and pages
about REVOKE. It will be looked at eventua
15 matches
Mail list logo
