Mark Knox <[EMAIL PROTECTED]> writes:
> I don't think this solution would be valid on many other platforms.
Au contraire --- the ARM is the first platform I've heard of that does
not think sizeof(ItemPointerData) is 6. Else we'd have seen this
regress test fail before.
> Well, this patch seems
At 12:27 AM 3/28/01 -0500, Tom Lane wrote:
>That would fix it for ARM but not for anyplace else with similar
>alignment behavior. Would you try this patch instead to see what
>happens?
I don't think this solution would be valid on many other platforms. It forces the
structure to not be padded,
On Wed, Mar 28, 2001 at 07:12:39PM -0500, Tom Lane allegedly wrote:
> Mathijs Brands <[EMAIL PROTECTED]> writes:
> > mathijs297 0.1 0.2 6120 3352 pts/1S 01:59:18 0:00
>/opt/pgsql/bin/./postgres mathijs localhost template1 idle
>
> The interesting point about this is that the 7.0.3-on-
> Larry Rosenman <[EMAIL PROTECTED]> writes:
> > FYI, the WU-FTPD code (2.6.0 or better) has a couple of more platforms
> > including UnixWare. The UnixWare code will need /dev/kmem permission to
> > change it's stuff, so I don't know whether we want to do this or not, but
> > if people are lo
> Mathijs Brands <[EMAIL PROTECTED]> writes:
> > PS_USE_CLOBBER_ARGV -is- used on Solaris. I just checked.
>
> Hm. But 7.1 postgres backends fail to change their ps display?
> Does sendmail change its ps display on your machine?
Seems we could easily use the sendmail display to populate the ps
> > On Wed, Mar 28, 2001 at 05:33:05PM -0500, Bruce Momjian allegedly wrote:
> >> Sure 'ps -U' will work, but it was reported that on Solaris, plain ps
> >> can't show the postgres status display, while ucb/ps can. I don't need
> >> specific columns. What I need is the postgres status parameters
Alfred Perlstein <[EMAIL PROTECTED]> writes:
> If it for pgmonitor then you guys ought to just mark it broken on
> these platforms, the non-"ps based" solution could have been
> implemented with all the time wasted trying to get the "ps based"
> hack working. :(
My thoughts exactly ;-) ... I'm wi
Mathijs Brands <[EMAIL PROTECTED]> writes:
> mathijs297 0.1 0.2 6120 3352 pts/1S 01:59:18 0:00
>/opt/pgsql/bin/./postgres mathijs localhost template1 idle
The interesting point about this is that the 7.0.3-on-2.7 installation
*is* managing to change its PS display. So either Solaris
* Tom Lane <[EMAIL PROTECTED]> [010328 16:07] wrote:
> Larry Rosenman <[EMAIL PROTECTED]> writes:
> > FYI, the WU-FTPD code (2.6.0 or better) has a couple of more platforms
> > including UnixWare. The UnixWare code will need /dev/kmem permission to
> > change it's stuff, so I don't know whether
On Wed, Mar 28, 2001 at 06:48:27PM -0500, Tom Lane allegedly wrote:
> Mathijs Brands <[EMAIL PROTECTED]> writes:
> > PS_USE_CLOBBER_ARGV -is- used on Solaris. I just checked.
>
> Hm. But 7.1 postgres backends fail to change their ps display?
> Does sendmail change its ps display on your machine?
Larry Rosenman <[EMAIL PROTECTED]> writes:
> FYI, the WU-FTPD code (2.6.0 or better) has a couple of more platforms
> including UnixWare. The UnixWare code will need /dev/kmem permission to
> change it's stuff, so I don't know whether we want to do this or not, but
> if people are looking at t
Mathijs Brands <[EMAIL PROTECTED]> writes:
> PS_USE_CLOBBER_ARGV -is- used on Solaris. I just checked.
Hm. But 7.1 postgres backends fail to change their ps display?
Does sendmail change its ps display on your machine?
regards, tom lane
---(end o
On Thu, Mar 29, 2001 at 12:30:06AM +0200, Mathijs Brands allegedly wrote:
> On Wed, Mar 28, 2001 at 04:56:15PM -0500, Bruce Momjian allegedly wrote:
> > [ Charset ISO-8859-1 unsupported, converting... ]
> > > whats wrong with /usr/ucb/ps auxw | grep $PGUSER
> > >
> > > to get only the processes
On Wed, Mar 28, 2001 at 04:56:15PM -0500, Bruce Momjian allegedly wrote:
> [ Charset ISO-8859-1 unsupported, converting... ]
> > whats wrong with /usr/ucb/ps auxw | grep $PGUSER
> >
> > to get only the processes for PG?
>
> I can do that if there is no other option, but on my BSDI machine,
> re
> Bruce Momjian writes:
>
> > Can someone confirm that 'ps' status display doesn't work on Solaris,
>
> You may need to use /usr/ucb/ps. Last I checked there was no way to
> change the display of /usr/bin/ps.
I can do that, but I am told that /usr/ucb/ps does not allow me to
restrict the displ
Tom Lane writes:
> It seems that in pre-7.0 Postgres, this works:
>
> create table one(id int default 1, descr text);
> create table two(id int default 2, tag text) inherits (one);
>
> with the net effect that table "two" has just one "id" column with
> default value 2.
Although the liberty to d
Richard T. Robino writes:
> - A more specific postmaster startup for a normal make check which says
> whether inet or unix sockets will be used. If you aren't aware of the
> problem on solaris and don't check netstat, the message is generic and there
> is a socket file in /tmp regardless of what
Bruce Momjian writes:
> Can someone confirm that 'ps' status display doesn't work on Solaris,
You may need to use /usr/ucb/ps. Last I checked there was no way to
change the display of /usr/bin/ps.
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
--
"Mikheev, Vadim" <[EMAIL PROTECTED]> writes:
> Hm, you're right:
> http://www.postgresql.org/devel-corner/docs/postgres/xact-read-committed.html
> "Read Committed is the default isolation level in Postgres. When
> a transaction runs on this isolation level, a SELECT query sees only
> data committ
Tom Lane wrote:
> See past discussions about appropriate handling of unlabeled numeric
> constants. This is a tricky area that needs a thoroughgoing rethink.
> If you go into it with only "fix uint4" in mind then you will almost
> certainly make things worse.
Gosh, you were certainly right there
I just had a discussion with a user who doesn't want to update from
6.4.something to 7.0.* because 7.0 broke a feature he likes, namely
the ability to change the default value of a column inherited from
a parent table. It seems that in pre-7.0 Postgres, this works:
create table one(id int defaul
> Looking at the docs, I see that 'SERIALIZABLE' has the same visibility
> rules as 'READ COMMITTED', which is very confusing. I expect
Hm, you're right:
http://www.postgresql.org/devel-corner/docs/postgres/xact-read-committed.htm
l
"Read Committed is the default isolation level in Postgres. Wh
> > I don't think that we dare try to make any basic changes in
> > MVCC for 7.1 at this late hour, so Forest is going to have
> > to live with that answer for awhile. But I would like to see
> > a cleaner answer in future releases.
>
> Is it the MVCC's restriction that each query inside a functi
At 3/28/2001 09:52 AM, Joel Burton wrote:
>On Wed, 28 Mar 2001, Bruce Momjian wrote:
>
> > > Actually,
> > >
> > > This reminds me of something I have been meaning to ask. All the new
> > > performance features are cool, but what I really need are all the ALTER
> > > TABLE ... functions implement
Adriaan Joubert <[EMAIL PROTECTED]> writes:
> Uggh, this needs some help. I've got the problem that I can insert a
> value bigger than MAXINT into an int8 column, but when I try to do the
> same for a uint4 column, the parser coerces it into an int4, as in:
See past discussions about appropriate
> At this point I decided that somewhere in the definition of the type
> there must be a way of specifying how values can be transformed. Can
> anybody explain to me what I need to change to make this work? Without
> this ecpg cannot work with unsigned ints, so explicit casting is not an
> option.
On Wed, 28 Mar 2001, Bruce Momjian wrote:
> > Actually,
> >
> > This reminds me of something I have been meaning to ask. All the new
> > performance features are cool, but what I really need are all the ALTER
> > TABLE ... functions implemented. In 7.0.x you could only add columns and
> > fore
Uggh, this needs some help. I've got the problem that I can insert a
value bigger than MAXINT into an int8 column, but when I try to do the
same for a uint4 column, the parser coerces it into an int4, as in:
test=# insert into tint8 values (3043140617);
INSERT 30254 1
test=# insert into tuint4 va
Hiroshi Inoue wrote:
> Lamar Owen wrote:
> > H. Hiroshi committed an update to GNUmakefile to 'enable multibyte
> > support' for ODBC. But that was only 33 hours ago -- meaning it wasn't
> > updated in time for RC1. Lessee. I'm rebuilding RC1 with Hiroshi's
> > GNUmakefile change as part
> In any case, a unified or context diff against the 7.1beta4 spec would
> be useful.
OK, here is a context diff of the spec file (note only two lines
changed). This addresses the "-fno-fast-math" problem on Mandrake (at
least 7.2 and earlier), and the "disappearing Pg.bs file" problem on
same.
Pete Forman writes:
> I've registered the result via the web form though the report is
> not accurate. Can somebody update the Remarks or Version field to
> indicate that I was using a snapshot rather than RC1 OOTB.
Further to that request, please ignore/delete the existing Remarks.
I have l
On 3/27/01 8:05 AM, "Tom Lane" <[EMAIL PROTECTED]> wrote:
> Alexander Klimov <[EMAIL PROTECTED]> writes:
>> Yes, it was really just incidence -- I try again, and 15 of 15 `make
>> check' passed with TCP sockets, but only 3 of 15 passed with UNIX
>> sockets. So, final decision is `Unix sockets are
> Actually,
>
> This reminds me of something I have been meaning to ask. All the new
> performance features are cool, but what I really need are all the ALTER
> TABLE ... functions implemented. In 7.0.x you could only add columns and
> foreign keys. You couldn't drop anything or add stuff like
Tom Lane writes:
> Pete Forman <[EMAIL PROTECTED]> writes:
> > The regression test is failing early on, during initdb. The core
> > file indicates that there is a SIGBUS. Hopefully the bugs fixed
> > as a result of the "More bogus alignment assumptions" thread will
> > sort things out.
>
Ooops, patch was the wrong way round. Here is a better one.
Sorry,
Adriaan
diff -Naur postgresql-7.1RC1.orig/src/interfaces/ecpg/include/ecpgtype.h
postgresql-7.1RC1/src/interfaces/ecpg/include/ecpgtype.h
--- postgresql-7.1RC1.orig/src/interfaces/ecpg/include/ecpgtype.h Sun Jan 7
04:03
Hi,
I've been doing some tests with writing int8 to the database using
ecpg. This does not work if the long long variable is in a structure, as
it is not recognised as a simple type.
The patch is attached, but is not very satisfactory. Moving the
definition of
ECPGt_lon
36 matches
Mail list logo