(Moved to -hackers)
Log Message:
---
Tablespaces. Alternate database locations are dead, long live tablespaces.
Sweet :)
There are various things left to do: contrib dbsize and oid2name modules
need work, and so does the documentation. Also someone should think about
COMMENT ON TABLESPACE
Andrew Sullivan wrote:
> On Thu, Jun 17, 2004 at 01:12:10PM -0400, Bruce Momjian wrote:
>
> > Well, the bad news is that this backtrace isn't very useful.
>
> No kidding. It's pretty frustrating.
>
> > My only guess is that getaddrinfo in your libc has a bug somehow that is
> > corrupting the
[bcc to hackers, general]
A match made in heaven...
http://news.com.com/2110-7343_3-5236745.html
---(end of broadcast)---
TIP 8: explain analyze is your friend
On Wed, 2004-06-16 at 02:49, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > -finalaction refers to what to do when target is reached - the purpose
> > of this is to allow recovery of a database to occur when we don't have
> > enough space for all of the xlogs at once, so we need to d
On Thu, 2004-06-17 at 18:00, [EMAIL PROTECTED] wrote:
> On 16 Jun, Bruce Momjian wrote:
> > With today being June 16th, we are half-way into the one month extension
> > of the feature freeze, now scheduled for July 1. Here is the status on
> > the various outstanding features:
> >
> > Tablesp
On Wed, 2004-06-16 at 23:50, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > Is that something you'd be able to do as a starting point for the other
> > changes? It's easier for a committer to do this, than for me to do it
> > and then another to review it...
>
> I'm up to my eyeball
On Thu, Jun 17, 2004 at 01:12:10PM -0400, Bruce Momjian wrote:
> Well, the bad news is that this backtrace isn't very useful.
No kidding. It's pretty frustrating.
> My only guess is that getaddrinfo in your libc has a bug somehow that is
> corrupting the stack (hance the improper backtrace),
Andrew Sullivan wrote:
> On Mon, May 10, 2004 at 11:59:40AM -0400, Andrew Sullivan wrote:
> >
> > On the weekend, we ran a set of tests on the offending system to see
> > if we could re-create it. We set up the triggering conditions just
> > as they'd been when it happened, and alas, no segfault.
On 16 Jun, Bruce Momjian wrote:
> With today being June 16th, we are half-way into the one month extension
> of the feature freeze, now scheduled for July 1. Here is the status on
> the various outstanding features:
>
> Tablespaces - This has been in the queue since June 1 and should have
[EMAIL PROTECTED] wrote:
> On 16 Jun, Bruce Momjian wrote:
> > With today being June 16th, we are half-way into the one month extension
> > of the feature freeze, now scheduled for July 1. Here is the status on
> > the various outstanding features:
> >
> > Tablespaces - This has been in the
Hi all,
I have defined a datatype called "varcharci", shamelessly yanking the
input, output, recv and send functions from varchar. This means (as far
as I understand things) that this type is binary compatible with varchar.
As such, I used the following two lines:
create cast ( varcharci AS varc
On Mon, May 10, 2004 at 11:59:40AM -0400, Andrew Sullivan wrote:
>
> On the weekend, we ran a set of tests on the offending system to see
> if we could re-create it. We set up the triggering conditions just
> as they'd been when it happened, and alas, no segfault. So although
> this was pretty m
Hi all,
When I look at the int4 functions (int4in, int4out, int4send, int4recv),
they are all marked "immutable". Then again, when I look at the varchar
functions, the in and out functions are immutable, but the send and
receive functions are stable.
Is there a reason for this?
Shac
Shachar Shemesh wrote:
> According to the docs, domains are not meant for that purpose, but
> for changing constraints of a type. Is it possible to define a domain
> that will have the same defaults and constraints as the base type,
> but will have different comparison functions? Will that provide
Hi all,
A while back I asked about creating a case insensitive postgresql. Tom,
at the time, suggested I create a case insensitive type instead.
I am now trying to go that route, and am wondering whether domains will
provide a shortcut for me. As far as I understand the task at hand, I am
quite
I'm describing view using the following SPI function.
All is fine except "attrelid" is everywhere set to 0. What I'm doing wrong ?
How can I get table oid and column id for every column in SQL result ?
PG_FUNCTION_INFO_V1(check_view);
Datum
check_view(PG_FUNCTION_ARGS)
{
int spiR
I think this is wrong, primarily because it's gonna be seriously
incompatible with existing dump files. The existing technique is
that each TOC entry says who owns the object. You should use that
information and not have to rely on new additions to the file format.
This is why GRANT/REVOKE has t
17 matches
Mail list logo