imited in scope static analysis for the cases where
it's possible to do so would be great. With pg_depend tracking so that
you know you're doing something wrong at DROP FUNCTION time.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
--
n one cidr/inet ranges, so it won't be of much use.
Have you tried using the ip4r extension yet?
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes
Dimitri Fontaine writes:
> Side note: as soon as we have CREATE EXTENSION AS $$ script $$; we will
> be able to add those cases as regression tests. That's not the main
> usage of that feature, by far, but I can't resits the occasion :)
Oh, I did already mention it :)
that level. This combination of choices ensures that we'll get
> back valid reports of the old namespace for each object, and so the
> are-they-all-the-same logic in AlterExtensionNamespace still works.
See attached.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : E
is tracking attempt was also
trying to change pg_depend entries, I think that was in two separate
patches versions.
DIRTT: Do It Right This Time
Álvaro, do you want to be working on a master only version of the fix
or do you want me to?
Regards,
--
Dimitri Fontaine
Dimitri Fontaine writes:
> I think we shouldn't change the content of pg_depend lightly here, and
So here's a patch following that idea.
Even for TIP I don't want us to change how pg_depend tracking is done,
because I want to propose a fix for the pg_dump bug
y
AlterTableNamepace other than the table itself and its sequences are
Indexes and Constraints. Owned Sequence (serial) will get cared of by
the extension dependency walking code.
I'm going to have a try at that.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expert
in the manual case.
I think we need to share more code in between
AlterRelationNamespaceInternal and AlterTableNamespace, but I'm not sure
if that's not exactly what Álvaro did try with his _oid() attempt that
failed.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL :
the API
changes, you need to alter extension drop function in the script before
9.1.4).
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http
temp schema explicitly
created by the extension script too (IIRC you can actually do that): it
could be just about documentation, but if that's not too much contorting
the code it would be better to just ERROR out, I think.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL
ect sense in general but is a useless restriction
when executing an extension's script.
I consider that bugfix for back branches, by the way (well, 9.1).
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
--
Sent via pgsql-bugs mailing list
owing an error is the best
> thing. We could always relax that later, but going the other way might
> be problematic.
+1
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgre
ext))
{
/* If already a member of this extension,
nothing to do */
if (oldext == CurrentExtensionObject)
return;
The problem lies in catalog scans and SnapshotNow, I think.
"Robert Hopek" writes:
> coding), existing software, such as phpPgAdmin, are stuck only looking in
> /tmp for it.
Did you try host=/custom/path/to/the/socket/?
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
--
Sent via pg
Dimitri Fontaine writes:
> Also, \dx+ cube will not show all the operators and functions.
Some dependency information is indeed missing in pg_depend. Will look
at why tomorrow, day's over here.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et
atalog.regclass AND
refobjid = '16385' AND deptype = 'e'
dim-# ORDER BY 1;
Of course we didn't have that problem when we added extensions in (that
I remember of), so I'm now going to try and find when that did change…
Regards,
--
Dimitri Fontaine
http://2ndQuadran
with the
background process doing so itself).
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Josh Berkus writes:
> echo $TZ returns nothing. We've checked several Ubuntu systems, and it
> seems that Ubuntu does not set $TZ.
You can tweak that easily by editing /etc/postgresql/8.4/main/environment.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL
Tom Lane writes:
> Note that doing anything more than RAISE NOTICE or equivalent would
> imply a significant protocol change.
My understanding is that the standard allows multiple resultsets per
query, is that the protocol change you're talking about?
Regards,
--
Dimitri Fo
Steve White writes:
> It would be advantageous to have a portable, simple means of including
> a module from the distribution contrib/ directory.
Please have a look at the Extension patch section here:
https://commitfest.postgresql.org/action/commitfest_view?id=9
Regards,
--
D
're talking about a trigger
that looks at the column type here, it was a misplaced general advice.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to
THNAME'
> +LANGUAGE C;
You can also do AS 'MODULE_PATHNAME', 'c_function_name' and maintain a
single C function that copes with both timestamp and timestamptz
arguments, that's what I had in mind: you still declare two functions at
the SQL level, though.
Regards,
--
D
ith time zone
(1 row)
So I guess that you need to modify very little code to get the trigger
to work for both types.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make ch
Tom Lane writes:
> Any thoughts out there?
Color me slow, but I don't understand what allows an index creation on a
table to not systematically add a dependency entry for the index that
references the table.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : E
bles for postmaster process
# This file has the same syntax as postgresql.conf:
# VARIABLE = simple_value
# VARIABLE2 = 'any value!'
# I. e. you need to enclose any value which does not only consist of letters,
# numbers, and '-', '_', '.' in single quotes. S
eeRADIUS, use "radclient" to send the following text:
>
> User-Name = "bob"
> User-Password = "hello"
> Raw-Attribute = 0x0501
>
> The last bit is a malformed RADIUS attribute.
Would using this lib help here?
http://caca.zoy.org/wiki/zzuf
Regards
Dave Page writes:
> On Fri, Sep 24, 2010 at 6:28 AM, Peter Eisentraut wrote:
>> On tor, 2010-09-23 at 23:56 +0100, Dave Page wrote:
>>> > Surely the error message can be polished, though?
>
> How else would you suggest we find out what may go wrong on an
> unsupported platform?
My guess here is
Tom Lane writes:
> (BTW, I should think that iconv or some related tool would have a
> solution for fixing this miscoding; it's not an uncommon problem.)
I guess recode is handling that.
http://recode.progiciels-bpi.ca/manual/Universal.html#Universal
Regards,
--
dim
--
Sent via pgsql-bugs
Robert Haas writes:
> Suppose I have a server running 8.2 and I'm going to wipe it and
> install the latest version of $DISTRIBUTION which bundles 8.4.
[...]
> I'm sure someone will tell me my system administration practices suck,
> but people do these kinds of things, in real life, all the time.
Stephen Frost writes:
> If it's an option w/ a default of "off", then chances are the admin will
> get the failure you're talking about, realize there's an issue, but then
> have a way to actually *fix* the restore without having to hack up
> multi-gigabyte files using vi. If you'd like, you're w
Top posting, sorry for that.
--
dim
Le 10 juin 2010 à 03:40, Robert Haas a écrit :
On Wed, Jun 9, 2010 at 9:35 PM, Bruce Momjian
wrote:
Robert Haas wrote:
I think users would rather have the restore fail, and know right
away
they have an issue, than to do the upgrade, and find out lat
Craig Ringer writes:
>> - other products are happy to solve the DISTINCT restriction without
>> any hint as far as what the datatype really is
>
> ... and so is Pg. That's not the problem; Pg complains after resolving the
> SELECT DISTINCT, when it finds that it's trying to insert values of
Farid Zidan writes:
> I see no technical analysis in your response.
I made a clear reference to what others have been saying, and that you
have been refusing to read. I don't see any point in getting technical
again, as I'm sure you will refuse to understand what is happening to
you here.
But a
Robert Haas writes:
>> Well as Bruce said this option won't solve the OP's problem, unless the
>> application he's using for managing the backups do use the option.
>
> Well, that's a pretty trivial change to the backup script. +1 from me on
> providing a pg_dump option.
The application still ha
Farid Zidan writes:
> I am not asking you to re-write my sql so the bug will not show. I am
> presenting you with sql that fails and shows the bug. If every time
> someone reported a bug you ask them to re-write their sql so the bug
> is not hit, that would not eliminate the bug.
You're not readi
Alvaro Herrera writes:
> I don't think "dumps must be human-readable" is an argument to reject
> such a switch, as long as it's off by default. And I haven't seen any
> other valid argument either, so +1 from me.
Well as Bruce said this option won't solve the OP's problem, unless the
application
Stefan Kaltenbrunner writes:
> As in have a (hyptothetical) tracker being subscribed to -bugs (and maybe
> the other lists in the future as well) so the workflow would look like
> this:
Well there is a WIP to use an ArchiveOpteryX based solution to replace
the archives and get rid of the artifici
Chris Travers writes:
> Ok. Here is my application: I write a multi-currency accounting
> program backed by PostgreSQL. After 1.3 is released (2Q this year),
> we expect to be doing a full redesign.
>
> What I am thinking about is having a custom data type, something like:
I'd be interested in
"Timothy Seever" writes:
> CREATE FUNCTION testfunc() RETURNS setof tablec AS $BODY$ SELECT * FROM
> tablec; $BODY$ LANGUAGE 'sql' STABLE;
Common wisdom saith to never ever use "SELECT *" in your code. You just
found out a reason why.
Regards,
--
dim
--
Sent via pgsql-bugs mailing list (pgsql
Tom Lane writes:
> You would need to take that up with whoever packages Postgres for
> Ubuntu. It sounds like they have some glitch in the package setup.
> AFAIK, whoever that is doesn't read this list, which is mainly for
> upstream Postgres development.
I think Martin Pitt reads this list, he'
Adam Matan writes:
> But still, pg_config remains with the removed version, after postresql
> restart and even total reboot:
>
> $ pg_config
> BINDIR = /usr/lib/postgresql/8.4/bin
[...]
> This creates confusion with external software packages trying to use pgxs,
> for example.
> Any ideas how t
Peter Eisentraut writes:
> On sön, 2009-10-25 at 13:52 +, Peter Bengtson wrote:
>> It would be good if you to the page describing how a db dump is required
>> only for major verson upgrades, e.g. from 8.3.x to 8.4.x but not from, say,
>> 8.3.7 to 8.3.8, could add a proviso: a DB dump *is* nece
Tom Lane writes:
> "philip wright" writes:
>> Description:8.4.1 compile fails on debian can't find libdl
>
> Our Debian packager would certainly have complained before now if PG
> didn't build on Debian. I suspect that you have forgotten to install
> some needed support files. Does Deb
Hi,
"walkerlacombe" writes:
> Operating system: vista home premium
> Description:wrong password.
> Details:
>
> when i boot up my pc i have owner and postgresql as users.for postgresql i
> need a password. now when i downloaded postgresql i had to make 2 passwords.
> now , when i
Steve Purcell writes:
> # su - postgres -c "env PGCLUSTER=8.3/main pg_dump openx|env
> PGCLUSTER=8.4/main pg_restore -d template1 -C"
>
> And the debian pg_wrapper script ends up selecting the 8.3 pg_dump binary in
> the first case. I'll have to figure out if there's even a way to execute
> the
Hi,
While preparing a module which should make its way to pgfoundry CVS soon
(BSD licenced), I stumbled accross a naming problem when using
custom_variable_classes.
It'll actively refuse the name if it contains an underscore (_):
ERROR: unrecognized configuration parameter "pre_prepare.relation
Hi,
We've been hit by a pg_freespacemap contrib module crash (SIGSEGV), gdb showed
it was in line 162 of it's pg_freespacemap.c file.
fctx->record[i].reltablespace = fsmrel->key.spcNode;
Thanks to Andrew Gierth (irc:RhodiumToad) and after some analysis and we've
been able to understan
Hi,
Le Monday 17 December 2007 19:05:36 chris wood, vous avez écrit :
> Hi, I found this bug? In beta 3. I am not a Linux guru so installing any
> betas in Debian is very painful for me. Perhaps you could check to see if
> it is still there in beta 4??
The experimental sources of debian already
48 matches
Mail list logo
