liar with the code and who
could code C, which I can't otherwise I'd do it), avoid potentially
silent bugs in shell scripts and would massively assist in the efficient
manipulation of in-place PostgreSQL databases.
I hope someone agrees with me :)
السلام عليكم
- Naz.
--
Sent
7;s data dir or something silly like that) expecting the wrong version.
I don't see how, if it were reduced to a single line, the indication of
version number could possibly be considered problematic under any
circumstances.
Regards,
- Naz.
--
Sent via pgsql-hackers mailing list (pgsql-h
Alvaro Herrera wrote:
Naz Gassiep wrote:
It may also be beneficial to add the ISO 3166 column into that view, the
data is in zone.tab and I can't see a reason to not include it.
We also have the country name in iso3166.tab and the geo coordinates.
And there is also a comment
Tom Lane wrote:
Naz Gassiep <[EMAIL PROTECTED]> writes:
I think that it would be great if the pg_timezone_names and
pg_timezone_abbrevs included a boolean field indicating if that item is
in the Olsen DB
Huh? They're all in the Olsen DB
Not true, the zone.tab file ha
as or other added item. This
would make it far easier to integrate the data in the view with external
data sources that also use the Olsen DB.
It may also be beneficial to add the ISO 3166 column into that view, the
data is in zone.tab and I can't see a reason to not include i
ngs
like using CLDR data and other standardized data sources easier, as you
could be confident that all timezone names matched the data in the CLDR.
I think what I'm trying to say is that using and applying standards is a
good thing.
- Naz.
Naz Gassiep wrote:
Is there any reason that the
Is there any reason that the zone.tab information is not included in the
pg_timezone_names system view? ISTM that there is really no reason not
to, as that view is really populated using that file anyway. There is a
1:1 mapping (assuming the aliases are mapped to the zone.tab entries
they are a
The problem with forcing authentication is that an auth-unaware client
connecting to a legitimate postmaster would have its connections
refused. That same client would have its connections accepted by an
impostor postmaster. Thus, there is no way to stop impostor postmasters
from carrying out t
Wow... not sure how I missed that. I *did* create this schema ages ago,
perhaps it wasn't there, or at the time I had no idea what the
implications were. *shrug*
Regards,
- Naz.
Tom Lane wrote:
Naz Gassiep <[EMAIL PROTECTED]> writes:
As a result, when creating tables
> Actually I think the *most* important thing to work on is to get hash to
> the point where its search speed actually beats btree consistently, so
> that it has an excuse to live. If that is insoluble we might well end up
> ripping it out entirely. (The first three TODO items for hash indexes
>
Just a question, is there any advantage to having this then building a
function in applications that wrap and use pg_dump with a few options?
Surely that's a more appropriate way to achieve this functionality?
- Naz.
Usama Munir wrote:
> Hi,
>
> i was following a thread some
; for a counterexample).
Yep. For the record, Ponzi died in poverty, so it's not a counter
example, just proves that any gains that are had will be short lived and
increase the size of the crash when crunch time comes. :)
- Naz.
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Andrew Dunstan wrote:
> Naz Gassiep wrote:
>> I believe the suggestion was to have an automated process that only ran
>> on known, sane patches.
> How do we know in advance of reviewing them that they are sane?
Same way as happens now. I would assume this mechanism would only be
rface sooner,
and as it would require zero work once set up besides system maintenance
(which should be low if it is implemented in a reasonably intelligent
manner) I feel that it is a great idea. Generally, I am all for
automating mundane tasks as much as possible.
Regards,
- Naz.
Andrew Dunstan
A few of us on IRC were wondering what the status of tsearch2 is in 8.3 ?
Was it decided to include it in core or did we decide to keep FTS as a
plugin?
Some brief comments from anyone on the inside of the whole FTS issue
would be greatly appreciated by us mere end users.
Regards,
- Naz
Granted, but a configure switch would allow users who want to use OS TZ
file in conjunction with a compiled from source installation. Many
users of OSes with package managers such as Debian or RedHat may, for
whatever reason, want to use a source tarball to install and also use
the OS TZ list.
ffer if we start drifting away from standards compliance.
Just my 2 rupees. :)
- Naz
Nikita wrote:
Few things from our side:
1. 'Skyline Of' is a new operator proposed in ICDE 2003, one of the
topmost conferences of Data Engineering. Skyline operation is a hot
area of resear
them
+1 on the need for more doc on the website about each of them, onus
falling on module authors, perhaps require at least a basic doc patch as
a requirement for /contrib inclusion.
- Naz
---(end of broadcast)---
TIP 9: In versions below 8.0
nvironment property. Why can't a counter be used for this instead?
- Naz.
Jan Wieck wrote:
For a future multimaster replication system, I will need a couple of
features in the PostgreSQL server itself. I will submit separate
proposals per feature so that discussions can be kept focused on o
None, but feel free to start coding for 8.3.My coding skills are still nascent,
but I shall do my best.
My coding skills are still pretty nascent, but I shall do my best.
That seems like a rather spectacular overstatement of the likely
benefits, not to mention a misdescription of what was di
Zero, because feature freeze is over.
Aah yes, fair enough
If you find this feature interesting, you are free to drive the development
yourself, independent of it appearing on any list. To avoid tears later on,
look for a consensus about the merit of the feature first, though
This has be
At risk of being chastised for reviving old issues, I was wondering,
what are the chances were of getting the dump / restore selectivity into
8.2 ? I am referring to the idea that, instead of the current 2 parts, a
dump could be broken up into 3 parts, namely tables, data and everything
else, s
Aah, sorry, I don't watch dev progress very closely. This is something
that has been bugging me since 7.4.x branch and I never got around to
whining about it. Consider my comments retracted.
- Naz
---(end of broadcast)---
TIP 6: explain analyze is your friend
Actually, what that view gives you is timezone offset abbreviations, not
the full zone names that you could use with SET TIME ZONE. It strikes
me that we should have a view for that as well. We could use code
similar to scan_available_timezones() to generate the view output.
It's somewhat urg
Martijn van Oosterhout wrote:
In the CVS version there is a table with this information:
http://developer.postgresql.org/pgdocs/postgres/view-pg-timezonenames.html
Great, thanks for that
Err, where does postgres use this information? I beleive there is a
project on pgfoundary that has som
Any chance for a DB Client accessible list of allowable time zones? I've
been told that the only way to get at this list is by looking through
the source and lifting the list from zone.tab.
While I'm at it, how about an accessible list of country codes? I know
that it's not core db functionali
Douglas McNaught wrote:
Naz Gassiep <[EMAIL PROTECTED]> writes:
I have a PostgreSQL installation on a Debian box that had the 64bit
SMP kernel installed before PostgreSQL was compiled and installed on
it. Does PostgreSQL take any advantage of the 64 bit environment or
have
I have a PostgreSQL installation on a Debian box that had the 64bit SMP
kernel installed before PostgreSQL was compiled and installed on it.
Does PostgreSQL take any advantage of the 64 bit environment or have we
not done anything to move into the 64 bit world yet?
Regards,
- Naz
dea finds its way to the appropriate developer and
doesn't get forgotten in the mountain of ideas in the "that'd be nice
to have some day" category?
- Naz
Andrew Dunstan wrote:
We already have a highly selective and configurable restore mechanism,
using the -L feature of pg_restore. Maybe there's a good special case
for this particular split, but it is hardly undoable now.
As for Naz' needs - I gave him a perl script I whipped
Andreas Joseph Krogh wrote:
On Friday 18 August 2006 18:52, Tom Lane wrote:
Naz Gassiep <[EMAIL PROTECTED]> writes:
I propose that two more be added:
--tables-only
--constraints-only
This doesn't seem well-defined at all. There are many
Tom Lane wrote:
Naz Gassiep <[EMAIL PROTECTED]> writes:
I propose that two more be added:
--tables-only
--constraints-only
This doesn't seem well-defined at all. There are many objects in a
database that are definitely neither tables nor constraints, and it
This is my first post to a PostgreSQL mailing list, so please forgive me
if I have posted to the wrong place
Currently pg_dump has flags for dumping only table definitions and/or
data. These flags are respectively:
--schema-only
--data-only
I propose that two more be added:
--tables-only
--co
33 matches
Mail list logo
